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 173935 - AWT thread blocked for 132576 ms.
Summary: AWT thread blocked for 132576 ms.
Status: CLOSED DUPLICATE of bug 173932
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-10-07 09:11 UTC by gtg
Modified: 2010-05-06 08:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 159678


Attachments
nps snapshot (29.32 KB, bin/nps)
2009-10-07 09:11 UTC, gtg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gtg 2009-10-07 09:11:20 UTC
Build: NetBeans IDE Dev (Build 200910061401)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02, Java(TM) SE Runtime Environment, 1.6.0_15-b03
OS: Linux, 2.6.27.29-0.1-default, amd64
Maximum slowness yet reported was 132576 ms, average is 132576
Comment 1 gtg 2009-10-07 09:11:25 UTC
Created attachment 88972 [details]
nps snapshot
Comment 2 Vitezslav Stejskal 2009-10-07 12:36:14 UTC
Not sure what is wrong - o.n.m.debugger.jpda.breakpoints.PersistenceManager.storeBreakpoints() listens on document
changes (ok) and schedules a task for storing breakpoints (probably?), which ends up in o.o.u.RP$SlowItem.<init>()...
Comment 3 Martin Entlicher 2009-10-07 16:23:58 UTC
Wrong is RP$SlowItem.<init>()!
But since this occurs almost everywhere, I've prepared a workaround for that in issue #173932.
Comment 4 Martin Entlicher 2009-10-07 16:32:34 UTC

*** This issue has been marked as a duplicate of 173932 ***
Comment 5 Marian Mirilovic 2010-05-06 08:02:37 UTC
verified duplicate