Bug 206137 - Debugger start is blocked by projects scan
Debugger start is blocked by projects scan
Status: RESOLVED FIXED
Product: debugger
Classification: Unclassified
Component: Java
7.1
PC All
: P3 (vote)
: 7.2
Assigned To: Martin Entlicher
issues@debugger
: PERFORMANCE, PLAN
Depends on:
Blocks: 202573
  Show dependency treegraph
 
Reported: 2011-12-08 14:00 UTC by Martin Entlicher
Modified: 2012-01-17 16:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments
Project scanning blocking debugger start. (2.95 KB, text/plain)
2011-12-08 14:00 UTC, Martin Entlicher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Entlicher 2011-12-08 14:00:23 UTC
Created attachment 113952 [details]
Project scanning blocking debugger start.

Until the project scan completes, it's not possible to start debugging.
This occurs when there are breakpoints submitted. The start of the debugger is blocked by identification of classes in debugger's sources.
It's apparent from the attached thread dump.
Comment 1 Martin Entlicher 2012-01-13 18:02:46 UTC
This matters only when Compile on Save is off. Otherwise Run and Debug actions wait for project scan & build.
Comment 2 Martin Entlicher 2012-01-16 13:30:09 UTC
When submitting breakpoints to the starting debuggee, it's necessary to be able to check the class names in the debug sources. The performance should be improved by using shared task, it is not blocked by the full scanning now.
changeset:   210532:0b55bb290a58
http://hg.netbeans.org/main/rev/0b55bb290a58
Comment 3 Quality Engineering 2012-01-17 16:11:26 UTC
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/0b55bb290a58
User: mentlicher@netbeans.org
Log: #206137 Use shared task to improve performance.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo