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.
NetBeans 6.7 Beta build 1) start the IDE with fresh userdir 2) open CustomerDB project from disk 3) IDE says Activating Java EE and open a modal dialog => IDE is frozen and nobody can do anything in IDE
Created attachment 80568 [details] Full thread dump (2x)
There seems to be more than one problem in this issue. Maybe fixing one of them is enough, but probably all shall be somehow addressed. #1 - MenuBar blocks AWT by waiting on folder recognizer. This btw. causes "UI freezing" - e.g. progress bars not moving, etc. #2 - profiler and project integration is eagerly initializing itself in folder recognizer which effectively blocks it. Probably the initialization shall be more lazy. I'll see what I can do with #1 and then pass the issue on.
I have implemented #2 in core-main#90c6f7a4549b - initialization of the action is now delayed till AWT thread. I have reported problem #1 as issue 163367 I guess this issue is fixed, however I cannot verify, as I do not know where to find CustomerDB project.
Integrated into 'main-golden', will be available in build *200904230201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/90c6f7a4549b User: Jaroslav Tulach <jtulach@netbeans.org> Log: #163201: Don't initialize MainProjectAction from outside of AWT thread
Reproduced again in NetBeans IDE Dev (Build 090423), see the attachment.
Created attachment 80753 [details] dumptStack.txt
This deadlock is slightly different: happens "later", but related to the original one. I'll work on it today. Meanwhile, can you Jirko try to reproduce it with following patch? http://www.netbeans.org/nonav/issues/showattachment.cgi/80681/X.diff Thanks a lot.
I'll apply this fix and let you now promptly.
I managed to simulate this kind of deadlock in a test. I can also confirm that fix similar to the above one solves the artificial deadlock. Jirka needs to verify if it solves the real deadlock as well, as I have not managed to reproduce it. Opening CustomerDB works without problems on my computer.
I haven't reproduced it with this patch anymore. It seems be a proper fix of this problem. Thanks
Hurá: core-main#991208ce71b4
Integrated into 'main-golden', will be available in build *200904250201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/991208ce71b4 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #163201: Don't wait from LazyMenu when doing own changes like updating own displayname or icon