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.

Bug 93453 - Explorer not responsive
Summary: Explorer not responsive
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: J Bachorik
URL:
Keywords: PERFORMANCE, THREAD
: 108642 109804 109967 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-29 15:56 UTC by Jan Becicka
Modified: 2007-09-13 07:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Full Thread Dump (27.59 KB, text/plain)
2007-01-29 15:56 UTC, Jan Becicka
Details
Fresh dumps (111.29 KB, application/octet-stream)
2007-02-21 13:28 UTC, Jan Becicka
Details
Fresh dumps (111.29 KB, text/plain)
2007-02-21 13:28 UTC, Jan Becicka
Details
couple of thread dumps (52.16 KB, text/plain)
2007-07-12 14:02 UTC, Milan Kubec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Becicka 2007-01-29 15:56:02 UTC
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.
Comment 1 Jan Becicka 2007-01-29 15:56:36 UTC
Created attachment 37782 [details]
Full Thread Dump
Comment 2 Jan Becicka 2007-01-29 16:01:33 UTC
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.
Comment 3 Milan Kubec 2007-02-12 15:00:51 UTC
Radime, do you have any idea how those inactive RP from Hacks$1 get created?
Comment 4 Jan Becicka 2007-02-21 13:28:31 UTC
Created attachment 38757 [details]
Fresh dumps
Comment 5 Jan Becicka 2007-02-21 13:28:43 UTC
Created attachment 38758 [details]
Fresh dumps
Comment 6 _ rkubacki 2007-02-21 14:57:23 UTC
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.
Comment 7 Milan Kubec 2007-07-12 14:01:48 UTC
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.
Comment 8 Milan Kubec 2007-07-12 14:02:40 UTC
Created attachment 45010 [details]
couple of thread dumps
Comment 9 Jan Lahoda 2007-07-12 14:12:07 UTC
From the TDs, the Java infrastructure does what it is requested to do by the profiler.
Comment 10 Jiri Sedlacek 2007-07-12 14:24:19 UTC
*** Issue 108642 has been marked as a duplicate of this issue. ***
Comment 11 Jiri Sedlacek 2007-07-17 10:19:58 UTC
*** Issue 109967 has been marked as a duplicate of this issue. ***
Comment 12 Jan Becicka 2007-07-17 10:28:16 UTC
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.
Comment 13 J Bachorik 2007-07-25 08:58:27 UTC
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)
Comment 14 Jan Lahoda 2007-07-31 16:38:38 UTC
*** Issue 109804 has been marked as a duplicate of this issue. ***
Comment 15 Alexander Kouznetsov 2007-09-13 07:44:39 UTC
Verified with Beta1