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.
Initialization of Navigator window blocks AWT for ages. Can the updateContext be called outside of AWT thread?
Created attachment 68958 [details] Thread dump of the blocked AWT thread
I don't think so - it was designed to run in EQ.
It won't be easy to change architecture to call NavigatorPanel.panelActivated outside EQ and honestly, it doesn't make much sense to me. Incompatible API change that doesn't make sense - I'm against it. I think it should be fixed on the side of providers, I think they can show "please wait" and return from panelActivated quickly. Passing to java/navigation.
dsimonek: Thank you for your great idea: >I think they can show "please wait" and return from panelActivated quickly The problem is that this is exactly what we are doing, all the parsing is done asynchromously in JavaSource loop, the "slow" code is just a code where we are looking if the file has a classpath (is a valid java file). The question why is it so slow is rather for core team, but anyway everyone knows the answer.
http://hg.netbeans.org/main/rev/c9c70f7a7e83
Thanks for replaning out of AWT.
Integrated into 'main-golden', will be available in build *200809050201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/c9c70f7a7e83 User: Tomas Zezula <tzezula@netbeans.org> Log: #146063:Navigator blocks startup in AWT thread