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 started to be stuck between 126 and 128Mb of heap and the UI became very unresponsive. The attached thread dump, with 49 NbSwingWorker threads might have something to do with it. I took this thread dump during shutdown (which took several minutes after the UI was closed); during that time other apps on my machine were considerably slowed down. The problem became noticable after I installed contrib/whichproject, contrib/linetools and contrib/semicolon, though I don't know if that was the trigger for something.
Created attachment 43217 [details] Thread dump
The reason behind this is that the Retouche infrastructure blocks any incoming calls for indeterminately long time. All those NBSwingWorkers should have been finished in few milliseconds. Anyway, I'll put a restriction on the number of active threads - this will avoid creating excessive number of new threads but sometimes can cause the UI become unresponsive till the Retouche infrastructure allows our code to make a query.
Sounds like you need to move as much of that work on a background thread as possible - which you're already doing; any UI which depends on work on a background thread should show some sort of "please wait" status, but certainly shouldn't be blocking the AWT thread.
Actually, this seems to be a duplicate of the issue #100077 Next time, plz, attach also the NB and Profiler build numbers. *** This issue has been marked as a duplicate of 10077 ***
Tim, what really causes your problem is most probably this: http://www.netbeans.org/issues/show_bug.cgi?id=105234
> *** This issue has been marked as a duplicate of 10077 *** I can't find anything in issue 10077 that even looks related to this issue. Is this a joke? Petr N's analysis seems like it might be on target. But I have no idea how an issue filed in March, 2001 about a dialog appearing on startup could have anything to do with this.
I think you meant issue 100077, not 10077.
Setting history straight *** This issue has been marked as a duplicate of 100077 ***
Verified duplicate