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 188352 - [69cat] AWT thread blocked for 41772 ms.
Summary: [69cat] AWT thread blocked for 41772 ms.
Status: RESOLVED INVALID
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-07-04 03:10 UTC by Exceptions Reporter
Modified: 2010-07-13 09:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 164230


Attachments
nps snapshot (31.96 KB, application/nps)
2010-07-04 03:10 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2010-07-04 03:10:42 UTC
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07
OS: Windows 7

User Comments:
GUEST: ?????

GUEST: ???



Maximum slowness yet reported was 41772 ms, average is 14064
Comment 1 Exceptions Reporter 2010-07-04 03:10:47 UTC
Created attachment 100590 [details]
nps snapshot
Comment 2 Jan Stola 2010-07-13 09:07:31 UTC
The attached snapshots do not show any clear problem in NetBeans.

The slowness reports 341892 and 403936 barely exceeded the threshold for a slowness report and both show the well-know fact that loading of the form (and creation of its UI) can block AWT thread for a while.

The slowness report 325572 has a high std. deviation of delays between samples, i.e., it shows biased data (probably because it was taken when the CPU was overloaded).

Finally, the report 407146 shows unreasonable amount of time spent in I/O calls. Hence, it seems that it was taken during intense disk usage (caused possibly by OS or another application) => closing this issue as invalid.