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.
Summary: | [69cat]AWT thread blocked for 4047 ms. | ||
---|---|---|---|
Product: | java | Reporter: | misterm <misterm> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jglick, misterm, tzezula |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 157024 |
Attachments: |
nps snapshot
nps snapshot |
Description
misterm
2009-11-30 06:38:51 UTC
Created attachment 94688 [details]
nps snapshot
Created attachment 95278 [details]
nps snapshot
Most of the time spent in the debug panel ClasspathNavigatorProviderImpl.getComponent which is not a part of an official build. The ClassMemberPanel time is class loading. Official build == release. The ClasspathNavigatorProviderImpl is not a part of a release only dev builds. (In reply to comment #3) > Most of the time spent in the debug panel > ClasspathNavigatorProviderImpl.getComponent I don't have the Navigator window visible (I keep it in sliding mode), yet the IDE is spending time updating it. This is a bug. Work should be done on Navigator views iff it is showing. >I don't have the Navigator window visible (I keep it in sliding mode), yet the IDE is spending time updating it.
1st) I will not do any changes to ClasspathNavigatorProviderImpl as it's not a part of release as mentioned above.
2nd) If the navigator is active even when closed (hidden) what has this in common with java.project?
I do not understand. If the navigator computes the panel content, it is a bug in the navigator that it asks the panels to initialize. See bug #172822. I have no idea how this could be fixed in java support (and esp. for the classpath panel which is driven solely from the navigator). *** This bug has been marked as a duplicate of bug 172822 *** |