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 169153

Summary:	[67cat] AWT thread blocked for 3515 ms.
Product:	platform	Reporter:	giorgio42 <giorgio42>
Component:	Module System	Assignee:	Jesse Glick <jglick>
Status:	RESOLVED WONTFIX
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
URL:	http://statistics.netbeans.org/exceptions/detail.do?id=154201
Issue Type:	DEFECT	Exception Reporter:	154201
Attachments:	nps snapshot

Description giorgio42 2009-07-24 22:52:38 UTC

Build: NetBeans IDE Dev (Build 090724)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows Vista, 6.0, amd64

User Comments:
giorgio42: Clicking on the Projects tab after having NB left alone for about half an hour.
This is on a core i7 920 box with 6 GB RAM.


Maximum slowness yet reported was 3515 ms, average is 3515

Comment 1 giorgio42 2009-07-24 22:52:43 UTC

Created attachment 85199 [details]
nps snapshot

Comment 2 Vitezslav Stejskal 2009-07-27 12:42:47 UTC

I can see that the total amount of time spent in AWT is 2311 and at least 409 + 721 + 299 = 1429 ms of that time is
spent on classloading. I'm not sure if this is normal or not. Maybe the JVM/classloader GCed some unused classes and
needed to load them again when you came back to the IDE. I'm not sure if this can or even should be prevented. From my
standpoint this is WONTFIX.

Comment 3 Jesse Glick 2009-07-27 17:11:47 UTC

Agreed, I don't see anything to optimize here. Classes are not GCd but there might have been classes not yet loaded.