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.
After a bit of investigation what is happening on start, I think I found one of the biggest contributors to recent (between 6.1 and 6.5) start slowdown. The commit bellow, changes BadgingNode to query for its Project in lookup. This happens in AWT thread during initialization and is highly visible, especially during cold start. # HG changeset patch # User Jesse Glick <jglick@netbeans.org> # Date 1210956601 14400 # Node ID 585ba313709f3542293b144c071add358603506d # Parent a9e78cc20869f04f2b76c96e768f1eae21acd1cc Badge project root nodes acc. to filesystem status automatically. Do not require every project type to do this individually. Other nodes which represent collections of files (but are not DataNode's) may still need special logic for now.
Maybe you have noticed that after the start the main window is shown, but its content remains grey. This is (together with other reasons) caused by this change. The AWT thread is blocked significantly, as following thread dump shows.
Created attachment 68708 [details] Stack trace of AWT thread
There are probably many ways to fix the problem, but I guess one of the most compelling for me is: show sand clocks while the node represents lazy node and only when it is fully initialized, switch to regular badge.
Is there a particular way to tell that the project has been "initialized"?
Trying to fix. Not sure how to reproduce, and I don't know much about LazyProject, so just guessing. core-main #0d6f5c004230
Integrated into 'main-golden', will be available in build *200809061401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/0d6f5c004230 User: Jesse Glick <jglick@netbeans.org> Log: #145682: refine fix of #135399 to account for lazy projects.