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.
070115, Windows XP, Java HotSpot(TM) Client VM (1.6.0-rc-b97 mixed mode) I have several nb projects open in explorer. If I use cursor keys to navigate in explorer, UI responsiveness is really poor. According to http://performance.netbeans.org/processes/bug_priority_guidelines.html this issue is P2 I guess.
Created attachment 37782 [details] Full Thread Dump
FileOwnerQuery is probably too expensive to be called from event AWT-EventQueue. Moreover there are some inactive Request Processor Threads created from org.netbeans.modules.project.ui.Hacks$1 in the dump.
Radime, do you have any idea how those inactive RP from Hacks$1 get created?
Created attachment 38757 [details] Fresh dumps
Created attachment 38758 [details] Fresh dumps
Honza, can you attach messages.log? There is some code that starts a lot of java.util.Timer instances so we see a lot of these threads. It is not the biggest problem here but still worth fixing.
I've taken couple of thread dumps and almost all of them showed that heavy java parsing is hapening during browsing Explorer nodes by arrow keys. See attached thread dumps. FileOwnerQuery was already a bit optimized, see #97215. Please evaluate, Thanks.
Created attachment 45010 [details] couple of thread dumps
From the TDs, the Java infrastructure does what it is requested to do by the profiler.
*** Issue 108642 has been marked as a duplicate of this issue. ***
*** Issue 109967 has been marked as a duplicate of this issue. ***
IDE is not usable for me with profiler installed. I'm experiencing long UI hangs very often. It is P1 IMO: performance: Very bad UI responsiveness making the feature unusable I had to uninstall profiler.
Should be fixed in trunk. Will be propagated into NB build 20070726 Efficiency of enabling/disabling profiler related actions was significantly improved. Tested the responsiveness of IDE with 20+ NB projects opened and it seems fine. In case you still feel it's not fast enough, reopen this issue and the check for validity of profiler actions in a certain context will be postponed till the moment the action is actually executed (as Run or Debug actions do)
*** Issue 109804 has been marked as a duplicate of this issue. ***
Verified with Beta1