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 188216 - [69cat] AWT thread blocked for 21626 ms.
Summary: [69cat] AWT thread blocked for 21626 ms.
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-06-29 19:49 UTC by Exceptions Reporter
Modified: 2010-11-20 06:13 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 162042

Attachments
nps snapshot (95.62 KB, application/nps)
2010-06-29 19:49 UTC, Exceptions Reporter 		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 Exceptions Reporter 2010-06-29 19:49:44 UTC 
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) Client VM, 16.2-b04, Java(TM) SE Runtime Environment, 1.6.0_19-b04
OS: Windows XP

User Comments:
stefan79: Editing in Diff-Window.



Maximum slowness yet reported was 21626 ms, average is 9315
Comment 1 Exceptions Reporter 2010-06-29 19:49:54 UTC 
Created attachment 100497 [details]
nps snapshot
Comment 2 Martin Entlicher 2010-07-01 09:07:34 UTC 
runWhenScanFinished() returns Future. Therefore it should not block.
Comment 3 Jan Lahoda 2010-10-05 13:42:09 UTC 
Sorry, but the Javadoc of JS.runWhenScanFinished says that it runs the task on asynchronously only if it would be blocked by the background scan. Otherwise, it runs synchronously. The debugger seems to be competing with several J2EE computations (done in brackground thread), so adding J2EE on CC.
Comment 4 Martin Entlicher 2010-10-18 13:40:50 UTC 
Then the Future does not have much sense!
I do not care at all if it's blocked by a background scan or another task. If it returns Future, it should not block.
Comment 5 Tomas Zezula 2010-10-18 13:49:11 UTC 
It does, just read the javadoc.
Comment 6 Martin Entlicher 2010-10-27 15:00:13 UTC 
O.K. so I guess I need to call runWhenScanFinished() off AWT thread always.
Comment 7 Martin Entlicher 2010-11-19 18:18:40 UTC 
Parsing code is run always in an RP thread, we assure that AWT is always responsive.
Fixed in changeset:   182807:e71641eae135
http://hg.netbeans.org/main/rev/e71641eae135
Comment 8 Quality Engineering 2010-11-20 06:13:41 UTC 
Integrated into 'main-golden', will be available in build *201011200001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/e71641eae135
User: mentlicher@netbeans.org
Log: #188216 Scan the sources really lazily.