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 138496 - 100% cpu while debugging
Summary: 100% cpu while debugging
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 2 votes (vote)
Assignee: Daniel Prusa
URL:
Keywords: PERFORMANCE
: 137827 141658 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-27 15:40 UTC by Jaroslav Tulach
Modified: 2012-10-12 16:56 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump (21.96 KB, text/plain)
2008-06-27 15:41 UTC, Jaroslav Tulach
Details
stack trace number 1 (20.23 KB, text/plain)
2008-07-28 21:31 UTC, dkittle
Details
thread dump (18.31 KB, text/plain)
2008-07-28 21:32 UTC, dkittle
Details
threaddump-100cpu.txt (24.14 KB, text/plain)
2008-08-12 11:23 UTC, Martin Krauskopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2008-06-27 15:40:39 UTC
Please make the debugger work at least a bit. Whenever I try to use the new debugging window, I need to kill the IDE.
Comment 1 Jaroslav Tulach 2008-06-27 15:41:13 UTC
Created attachment 63604 [details]
thread dump
Comment 2 Daniel Prusa 2008-06-30 12:58:06 UTC
It seems that refresh of Debugging View is slow and occupies awt thread too much - needs to be optimized.
Comment 3 Peter Pis 2008-06-30 13:38:26 UTC
We have been able to reproduce similar problem while debugging many threads (over 100) then, the response was really
slow. For now we are downgrading this to P2.
Comment 4 Daniel Prusa 2008-07-03 09:49:18 UTC
*** Issue 137827 has been marked as a duplicate of this issue. ***
Comment 5 Martin Krauskopf 2008-07-03 09:58:02 UTC
> (over 100)

Debugging NetBeans in NetBeans, e.g. now I have 19 threads. And sometime it seems impossible to get rid of (close) the
Debugging View. Happens always when I forgot to close Debugging View immediately after debugging session starts up. Once
I forgot I usually have to kill the IDE.

Is there any trick how disable the Debugging View temporarily?
Comment 6 Martin Krauskopf 2008-07-15 10:55:33 UTC
Seems to work for me OK in latest trunk. FYI....
Comment 7 Daniel Prusa 2008-07-25 10:00:34 UTC
*** Issue 141658 has been marked as a duplicate of this issue. ***
Comment 8 dkittle 2008-07-28 21:30:29 UTC
I have this problem when debugging an enterprise application.

I set a couple of break points, one in the web application, one in the ejb application.  I right click the enterprise
application and select debug.

The project runs in debug mode, but the IDE goes to 100% CPU and stays there.  The IDE window no longer updates (or at
least it is REALLY slow and won't update in less than 30 seconds).  If I stop Glassfish (which ends the debug session)
the IDE is normal (the window refreshes and is no longer consuming 100% CPU).

I'm using:
Product Version: NetBeans IDE Dev (Build 200807281401)
Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\donk\.netbeans\dev

I'll attach two thread dumps.
Comment 9 dkittle 2008-07-28 21:31:38 UTC
Created attachment 65857 [details]
stack trace number 1
Comment 10 dkittle 2008-07-28 21:32:16 UTC
Created attachment 65858 [details]
thread dump
Comment 11 Daniel Prusa 2008-08-03 22:01:01 UTC
Fixed.
changeset a612f35a1ee5 in main
details: http://hg.netbeans.org/main?cmd=changeset;node=a612f35a1ee5
Comment 12 Quality Engineering 2008-08-04 03:58:08 UTC
Integrated into 'main-golden', available in build *200808040201* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/a612f35a1ee5
User: Daniel Prusa <dprusa@netbeans.org>
Log: #138496: Debugging View refresh optimized
Comment 13 Martin Krauskopf 2008-08-12 11:22:13 UTC
Reproducible again for last few (at least two) days. Attaching threaddump during the 100% CPU usage.

Fresh build from this morning:
Product Version: NetBeans IDE Dev (Build 080812)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b14
System: Linux version 2.6.24-19-generic running on i386; UTF-8; en_US (nb)
Comment 14 Martin Krauskopf 2008-08-12 11:23:08 UTC
Created attachment 67134 [details]
threaddump-100cpu.txt
Comment 15 Daniel Prusa 2008-08-12 11:50:49 UTC
Now it seems like a different problem. CPU is consumed by changes in nodes not by Debugging View repaint (stripes on the
left, suspend/resume icons on the right).
...
at org.openide.nodes.Node.fireShortDescriptionChange(Node.java:1000)
at org.netbeans.modules.viewmodel.TreeModelNode.refresh(TreeModelNode.java:354)
Comment 16 Martin Krauskopf 2008-08-12 11:57:54 UTC
I've reopened wrt. to the user's point of view - exactly the same issue. Let me now if you want me to file separate
request somewhere else.
Comment 17 Daniel Prusa 2008-08-12 12:06:29 UTC
No, it is ok, we will track it here. It was just an evaluation, not a complaint that you have reopened the issue ;-)
Comment 18 Daniel Prusa 2008-09-23 15:46:15 UTC
Debugging View performance seems to be ok in recent builds. Martin agreed to close this issue.
Comment 19 matusdekanek 2008-11-24 08:19:16 UTC
debugger seems to work fine
verifying
Comment 20 netbeans.89423 2012-10-11 13:35:52 UTC
Problem is there again with Netbeans 7.2 release. Maybe it is time to add a regression test.
Comment 21 Petr Cyhelsky 2012-10-11 13:38:35 UTC
(In reply to comment #20)
> Problem is there again with Netbeans 7.2 release. Maybe it is time to add a
> regression test.

can you please attach the .nps so that it can be evaluated?
Comment 22 Martin Entlicher 2012-10-11 13:39:50 UTC
Can you please submit a new issue with a slowness report attached? There were certainly big code changes between 6.5 and 7.2, therefore it's likely a different problem. Please provide the slowness report so that we can evaluate where the problem is.
Comment 23 netbeans.89423 2012-10-12 16:46:34 UTC
how do I create a slowness report?
Comment 24 Martin Entlicher 2012-10-12 16:56:52 UTC
The easiest way is to use the self-profiling feature:
http://wiki.netbeans.org/FaqProfileMeNow