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 169261 - AWT thread blocked for 3521 ms.
Summary: AWT thread blocked for 3521 ms.
Status: CLOSED WONTFIX
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@performance
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 20:26 UTC by kawazu428
Modified: 2011-05-25 11:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 154299


Attachments
nps snapshot (19.71 KB, bin/nps)
2009-07-27 20:26 UTC, kawazu428
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kawazu428 2009-07-27 20:26:51 UTC
Build: NetBeans IDE Dev (Build 200907270201)
VM: Java HotSpot(TM) Server VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Linux, 2.6.28-13-generic, i386

User Comments:
kawazu428: here we come again... ;) starting the ide (55 mvn2 projects, a handful of pom.xmls and "Start Page" opened at startup)


Maximum slowness yet reported was 3521 ms, average is 3521
Comment 1 kawazu428 2009-07-27 20:26:59 UTC
Created attachment 85273 [details]
nps snapshot
Comment 2 Tomas Pavek 2009-09-11 14:13:16 UTC
AWT thread painting for about 2s. It's not obvious why it takes so long. It does not seem that so much would be painted,
most of the time spent in native painting methods. Might be related to issue 171792. There's also one icon loading of
200ms (way too long as well).

In parallel most of time is spent in Maven collecting project dependencies, but that should not slow down the AWT thread
so much (it's I/O intensive).

It seems like the system was overloaded (also doing something else), hanging periodically, or doing GC... With new
snapshots we'd get more data about such conditions.

Closing this for now, not able to tell what the cause is. If this is happening often, we'll receive more snapshots.