This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Several people in NetCAT program reported that startup time of IDE is long and sometimes even confusing. It is displayed, seems to be ready but it takes 20 more seconds to become fully responsive. Could you please comment on this and improve the behaviour ?
Hi all, we need as much info as you can provide, like : OS, used JDK, IDE build number, additional modules, used switches, .... Thanks for cooperation ;) By the way, it isn't about startup time as defined by running command line until whole IDE is painted, but it's about !Warm Up! like a "UI responsiveness tax" I agree we should find some User freindly way to do it, what about informational dialog, or progress bar in status line ?
Assigning to performance component until we find a culprit of the problem.
I like your idea of a progress bar in the status bar. I find it less intrusive than popping up a dialog saying "Please wait..." :) My main complaint is that 3.6 feels more sluggish than 3.5.1 on my FreeBSD 5.2-RELEASE box (AMD Athlon XP1800+, 1024 mb RAM). I use the native JDK 1.4.2-p6 and KDE 3.2 as window manager. Sometimes the text editing is really slow, there can be a delay between pressing a key and getting the corrsponding letter in the editor. Switching between tabs, opening menus and performing other UI interaction also feels slow(er than it was in 3.5.1). Guess this is where a progress bar might be usefull, to at least let the user know that something is going on. I have no extra modules loaded, and I am using build 200402042050. Hope this helps!
I feel all operations are slow the first time. One you start the IDE, it takes about 25-30 secs (P3/512/Win2k/JDK1.4.2) to paint itself. The clicking the editor will again start some disk churning activity and it will be about 5-10 secs before you can edit files. I also notice that invoking a menu (once a menu is invoked, the rest come up quicly), using the "Go To Class" options, the richt click menu, tools->options all take more time the first time. And ofcourse, I notice these problems again when i get back to netbeans after a while of inactivity. This is not as bad on my P4-1.6/768/WinXp machine.
I would like to ask if you have some measures already prepared because tomorrow is the last working day when P3 fixes can be integrated. I have noticed that Target Milestone is still set as TBD so I hope you don't plan to ignore problems of at least 3 known people. Or are we supposed to upgrade the priority to P2 on Monday ?
Retargetting this issue for promo-D. Unfortunatelly we are not able to do anything about it for promo-B.
I have the same problem. After 35 sec the NB windows comes up and 60 sec later the hard disk activity comes finally to an end. The first time this happened (with NB 3.6 Beta) I thought NB has crashed... Here my specs: NB 3.6 RC1 (with default settings) JDK 1.4.2_04 Windows XP SP1 No background apps running (just the default Windows services) Hardware: Athlon XP 2600+, 1GB RAM. Feel free to ask if you have any questions!
I have to correct myself: The startup time changes with each start (with a boot between each start). They vary from 55 to 85 sec. I see no pattern here, even when I change the startup switches in the ide.cfg... Here's the ide.cfg: -J-Xms24m -J-Xmx96m -J-Xverify:none
On my machine it takes now 10 minutes to start netbeans.
The complaint here is about IDE startup that is actually longer than it seems because even when the IDE is started (and GUI displayed) there is continued activity that interefes with users work. This so called warmup is here to make access to various functionalities of the IDE faster. For example menus, editor opening... Probably the biggest improvement here can be rewrite of actions to make them more declarative. This is tracked in #70280. No other fixes are planned in a near future.
Okay, verified then.