This issue was originally marked as duplicate of issue 171690, that is already resolved. This issue is still valid, so this seems to be another issue, but it might be related.
Build: NetBeans IDE Dev (Build 091006)
VM: Java HotSpot(TM) Client VM, 1.5.0_20-b02, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_20-b02
OS: Linux, 2.6.28-15-generic, i386
jglick: Started IDE with several projects open; immediately selected them all and invoked File > Close - IDE hung.
Maximum slowness yet reported was 20582 ms, average is 20582
Created attachment 89219 [details]
Most of the time spent in apisupport, please evaluate. Thanks.
Just reported http://statistics.netbeans.org/analytics/exception.do?id=291407. Took 28251 ms, this is not a P3 problem -
it makes the user think the IDE is deadlocked and must be restarted.
What about just removing the "Close" action during the initialization if the performance is not easy to/cannot be
improved? The result will be the same as invoking "Close" after initialization except that EDT won't be blocked.
The problem is that closing projects runs in AWT thread and waits for projects to be loaded first in background. Formal
fix would be close projects in background too, but it doesn't really save any user's time - he still needs to wait for
all the projects to be loaded and then to be closed.
Better would be to really cancel loading projects that weren't loaded yet - don't know how big a change would that be.
*** Issue 174398 has been marked as a duplicate of this issue. ***
Created attachment 91903 [details]
Thread dump - one Maven project opened (Glassfish) and attempting to close another JavaApplication
At least recent snapshots seem to be about web projects doing a lot of work when opened. Perhaps some of it could be avoided or deferred.
No reports since 6.8. Likely fixed.