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 177846 - [69cat]AWT thread blocked for 4047 ms.
Summary: [69cat]AWT thread blocked for 4047 ms.
Status: RESOLVED DUPLICATE of bug 172822
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-11-30 06:38 UTC by misterm
Modified: 2010-05-04 17:10 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 157024

Attachments
nps snapshot (256.00 KB, application/nps)
2010-03-02 07:48 UTC, misterm 		Details
nps snapshot (256.00 KB, application/nps)
2010-03-17 11:39 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2009-11-30 06:38:51 UTC 

    


    


      



        
          Comment 1
        

        
          misterm

        

        
        

        
          2010-03-02 07:48:53 UTC
        

      






Created attachment 94688 [details]
nps snapshot

    


    


      



        
          Comment 2
        

        
          Exceptions Reporter

        

        
        

        
          2010-03-17 11:39:16 UTC
        

      






Created attachment 95278 [details]
nps snapshot

    


    


      



        
          Comment 3
        

        
          Tomas Zezula

        

        
        

        
          2010-04-16 14:04:52 UTC
        

      






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.

    


    


      



        
          Comment 4
        

        
          Tomas Zezula

        

        
        

        
          2010-04-16 14:06:56 UTC
        

      






Official build == release. The ClasspathNavigatorProviderImpl is not a part of a release only dev builds.

    


    


      



        
          Comment 5
        

        
          Jesse Glick

        

        
        

        
          2010-05-04 14:54:53 UTC
        

      






(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.

    


    


      



        
          Comment 6
        

        
          Tomas Zezula

        

        
        

        
          2010-05-04 15:08:43 UTC
        

      






>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?

    


    


      



        
          Comment 7
        

        
          Jan Lahoda

        

        
        

        
          2010-05-04 15:21:29 UTC
        

      






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).

    


    


      



        
          Comment 8
        

        
          Jesse Glick

        

        
        

        
          2010-05-04 17:10:48 UTC
        

      







*** This bug has been marked as a duplicate of bug 172822 ***