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 169034 - AWT thread blocked for 8�437 ms.
Summary: AWT thread blocked for 8�437 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-23 12:42 UTC by pribyl
Modified: 2009-07-27 09:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 154099


Attachments
nps snapshot (35.00 KB, bin/nps)
2009-07-23 12:42 UTC, pribyl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pribyl 2009-07-23 12:42:22 UTC
Build: NetBeans IDE Dev (Build 200907230201)
VM: Java HotSpot(TM) Client VM, 14.1-b02, Java(TM) SE Runtime Environment, 1.6.0_15-b03
OS: Windows XP, 5.1, x86

User Comments:
pribyl: Right after IDE start (2 really small project were opened)


Maximal alredy reported slowness was 8437 ms, average is 8437
Comment 1 pribyl 2009-07-23 12:42:34 UTC
Created attachment 85123 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2009-07-24 14:23:49 UTC
Form or multiview or JDK?
Comment 3 Tomas Pavek 2009-07-24 15:34:53 UTC
new javax.swing.JToggleButton taking 6 seconds? I have no idea what it could be. Stuck in native  
java.lang.Class.getInterfaces. I can see in another thread almost the same long wait (6s in 
java.io.WinNTFileSystem.canonicalize0). These methods should not take so long. Looks like the whole system froze for 6 
seconds... Something random, or GC?

Let us know if you see this again.
Comment 4 pribyl 2009-07-27 09:19:48 UTC
Well, it is random I guess. I tried the same situation (same projects opened, similar system conditions...) and it run
smoothly.

In fact, I almost did not realize the slowness in the first case, but the "slowness reporter" (or how it should be
called) encouraged me to report, so I obeyed :)

I'll let you know if I encounter this again, of course with some more useful description.