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 169126 - AWT thread blocked for 3579 ms.
Summary: AWT thread blocked for 3579 ms.
Status: RESOLVED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Hurka
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-07-24 14:08 UTC by kawazu428
Modified: 2011-05-25 11:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 154174

Attachments
nps snapshot (30.34 KB, bin/nps)
2009-07-24 14:08 UTC, kawazu428 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kawazu428 2009-07-24 14:08:30 UTC 
Build: NetBeans IDE Dev (Build 200907240201)
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: re-opening the project group (55+ maven2 projects, "folder-of-projects" group) after restart, while into "task scanning"...  - I wonder whether the fact that all these projects are under SVN control might add (negatively) to that time...


Maximum slowness yet reported was 3579 ms, average is 3579
Comment 1 kawazu428 2009-07-24 14:08:42 UTC 
Created attachment 85181 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2009-07-24 15:52:18 UTC 
When opening this snapshot I get following exception. Assigning to profiler to be more robust:

java.lang.ArrayIndexOutOfBoundsException: 857
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:413)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
	at org.netbeans.lib.profiler.results.cpu.CPUCCTContainer.addFlatProfTimeForNode(CPUCCTContainer.java:408)
Comment 3 J Bachorik 2010-10-08 12:25:13 UTC 
Fixed the problem with reading the snapshot - http://hg.netbeans.org/profiler-main/rev/6aefeec94171 . You can carry on analyzing the root cause for slowness.
Comment 4 Quality Engineering 2010-10-09 15:26:27 UTC 
Integrated into 'main-golden', will be available in build *201010090000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/6aefeec94171
User: Jaroslav Bachorik <yardus@netbeans.org>
Log: #169126: Reading a profiler snapshot is made a more robust to support certain corrupted self-profiling snapshots
Comment 5 Marian Mirilovic 2011-05-25 11:29:06 UTC 
just one problem reported so far .. closing as worksforme