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 137827 - 100% CPU utilization when Debugging View is shown
Summary: 100% CPU utilization when Debugging View is shown
Status: CLOSED DUPLICATE of bug 138496
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-20 15:36 UTC by Martin Krauskopf
Modified: 2010-04-29 09:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
threaddump.txt (20.65 KB, text/plain)
2008-06-20 15:36 UTC, Martin Krauskopf 		Details
four-threaddumps.txt (67.49 KB, text/plain)
2008-07-02 16:14 UTC, Martin Krauskopf 		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 Martin Krauskopf 2008-06-20 15:36:17 UTC 
It seems to happen always if I forgot to close Debugging View (A-S-9). Attaching threaddump during 100% CPU utilization.
Not sure if the same as issue 136652. But Jarda talks there about Thread View. So filling new one.

Workaround: closing Debugging View immediately after it appears after debugging session started

===========
Product Version: NetBeans IDE Dev (Build 080620)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b12
System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb)
Comment 1 Martin Krauskopf 2008-06-20 15:36:59 UTC 
Created attachment 63171 [details]
threaddump.txt
Comment 2 Daniel Prusa 2008-06-24 14:47:29 UTC 
AWT thread is blocked by JDI sending request to the debugged VM. This is caused by calling JPDAThread.getName() to
obtain tooltip text in ClicableIcon. In general, JDI calls should be outside AWT.

Im not sure if this can cause 100% CPU utilization, another reason could be that ui refresh was called frequently,
perhaps in neverending loop.
Comment 3 Daniel Prusa 2008-06-26 13:45:32 UTC 
Problem with JDI called from AWT fixed.
If it does not help and 100% CPU will still occur, attach a sequence of thread dumps (at least 4), please.

changeset 4690ac631485 in main
details: http://hg.netbeans.org/main?cmd=changeset;node=4690ac631485
Comment 4 Quality Engineering 2008-06-27 16:24:09 UTC 
Integrated into 'main-golden', available in NB_Trunk_Production #285 build
Changeset: http://hg.netbeans.org/main/rev/4690ac631485
User: Daniel Prusa <dprusa@netbeans.org>
Log: #137827: cache thread's name, refresh it on thread suspend
Comment 5 Martin Krauskopf 2008-07-02 16:14:56 UTC 
Created attachment 63826 [details]
four-threaddumps.txt
Comment 6 Martin Krauskopf 2008-07-02 16:17:28 UTC 
Product Version: NetBeans IDE Dev (Build 080701)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b12
System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb)
Comment 7 Daniel Prusa 2008-07-03 09:49:19 UTC 
Awt thread is busy at org.netbeans.modules.debugger.jpda.ui.debugging.DebuggingView$ViewRefresher.run(), this is the
same problem as reported in issue 138496. Refresh of Debugging view has to be optimized. 

*** This issue has been marked as a duplicate of 138496 ***
Comment 8 Quality Engineering 2010-04-29 09:40:26 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.