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.
It looks like we have another regression on Complex startup (measured for Java Application project as well as for NB project). First and subsequent startups are fine. Unfortunately changelog for this build is not available, so it would be difficult to find responsible person ;( Comparison between builds 200606061800 and 200606071800: Linux Win2K WinXP Startup Time with 10 opened java files 57 % 63 % 54 % Startup Time with opened NB project 57 % 55 % 54 %
Created attachment 30877 [details] HIstory for Complex startup with Java Project opened
Created attachment 30878 [details] HIstory for Complex startup with NB Project opened
Created attachment 30879 [details] startup log file for 200606061800 - Linux
Created attachment 30880 [details] startup log file for 200606071800 - Linux
If you compare attached logs : new @24199 - Main window initialization finished, took 11862ms old @21951 - Main window initialization finished, took 9517ms Well, if you loog at the log from our repaint manager, you'ld find more ... there are a lot off paints from progress bar after a 15s ;( <event diff="21099" name="addDirtyRegion org.netbeans.progress.module.ui.NbProgressBar, 0,0,133,19" time="1149745961032" type="TRACK_APPLICATION_MESSAGE"/>
Old, and obviously a problem of measurement infrastructure - the IDE was already started, just the background task was causing (tracked) repaints.
v/c