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 171436 - AWT thread blocked for 28358 ms.
Summary: AWT thread blocked for 28358 ms.
Status: RESOLVED DUPLICATE of bug 171183
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Lahoda
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-09-03 20:26 UTC by Michel Graciano
Modified: 2010-05-12 12:25 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 157653


Attachments
nps snapshot (128.97 KB, bin/nps)
2009-09-03 20:26 UTC, Michel Graciano
Details
nps snapshot (36.16 KB, bin/nps)
2009-10-03 11:50 UTC, dima_s_d_s
Details
nps snapshot (27.43 KB, bin/nps)
2009-10-06 21:02 UTC, dima_s_d_s
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2009-09-03 20:26:34 UTC
Build: NetBeans IDE Dev (Build 200909010201)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Linux, 2.6.28-15-generic, i386

User Comments:
GUEST: "applying changes" while in debug mode


Maximum slowness yet reported was 28358 ms, average is 19488
Comment 1 Michel Graciano 2009-09-03 20:26:40 UTC
Created attachment 87085 [details]
nps snapshot
Comment 2 Jan Lahoda 2009-09-21 10:06:00 UTC
Not related to Java support - if the Java support is asked to perform parsing in the AWT thread, it cannot do anything
but obey. Seems that the autosave module performs saveAll() in AWT thread, although this action is a background-like
action in this case (should not ideally be performed in the AWT thread, IMO). Passing there to investigate.
Comment 3 Michel Graciano 2009-09-22 02:59:07 UTC
I fixed the problem at autosave module but the problem I think is not related to it since just one of snapshot was fired 
by autosave module. BTW, thanks for point the problem at the module. If you have any comment about the fix, just let me 
know. I don't know if it should be marked as fixed, so fell free to reassign it.

main/contrib: #9ec34205c884
Comment 4 Michel Graciano 2009-09-22 03:02:40 UTC
I marked it as fixed but I am not sure about it. Sorry.
Comment 5 Exceptions Reporter 2009-09-30 17:33:39 UTC
This issue already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=157653
Comment 6 Michel Graciano 2009-10-01 17:19:00 UTC
As I said, I fixed it at autosave module but looks like another reports was sent even without autosave module installed. Reassigning back for evaluation.
Comment 7 dima_s_d_s 2009-10-03 11:50:03 UTC
Build: NetBeans IDE Dev (Build 200908022240)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments: 

Maximum slowness yet reported was 28358 ms, average is 12127
Comment 8 dima_s_d_s 2009-10-03 11:50:09 UTC
Created attachment 88783 [details]
nps snapshot
Comment 9 Exceptions Reporter 2009-10-03 11:50:14 UTC
This issue already has 6 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=157653
Comment 10 dima_s_d_s 2009-10-06 21:02:06 UTC
Build: NetBeans IDE Dev (Build 200908022240)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments: 

Maximum slowness yet reported was 28358 ms, average is 11794
Comment 11 dima_s_d_s 2009-10-06 21:02:10 UTC
Created attachment 88945 [details]
nps snapshot
Comment 12 Exceptions Reporter 2009-10-06 21:02:16 UTC
This issue already has 7 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=157653
Comment 13 Jan Lahoda 2010-05-12 12:25:00 UTC
The latest report is duplicate of bug #171183.

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