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 40196 - [36cat] CPU @ 100% while debugging
Summary: [36cat] CPU @ 100% while debugging
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-18 00:44 UTC by isullivan
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread Dump during excessive CPU usage. (26.62 KB, text/plain)
2004-02-18 00:45 UTC, isullivan 		Details
Thread Dump after stopping debug session (10.67 KB, text/plain)
2004-02-18 00:51 UTC, isullivan 		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 isullivan 2004-02-18 00:44:20 UTC 
[ JDK VERSION : J2SE 1.4.2_02 ]

While I was debugging my machine slowed to a crawl and I noticed that the IDE was using all of the CPU. I had been searching through the various debugging views looking for a way to control which class members (static, protected, inherited, etc) are displayed in the local variables view, at some point during that search is when the abnormal CPU usage began. When I stopped the debugging session the CPU usage went back down to normal. I'm attaching a Thread Dump during the debugging session, and one from right after I stopped the debugger. I was not able to easily reproduce this.
Comment 1 isullivan 2004-02-18 00:45:04 UTC 
Created attachment 13480 [details]
Thread Dump during excessive CPU usage.
Comment 2 isullivan 2004-02-18 00:51:04 UTC 
Created attachment 13481 [details]
Thread Dump after stopping debug session
Comment 3 Jiri Kovalsky 2004-02-18 13:18:45 UTC 
Could somebody please comment on this issue ?
Comment 4 Maros Sandor 2004-02-23 09:33:52 UTC 
There are 2 suspicious threads running: Java source parsing and 
Debugger request processor. As for the debugger thread, it runs 
periodically to update the Classes view and I do not see any problem 
in the stack trace. I will pass this to the Java module for 
evaluation of their thread's stack trace to make sure it is not 
problem in the parser.
Comment 5 Jan Pokorsky 2004-02-23 10:33:56 UTC 
When you took the second thread dump was the cpu free?
If it is reproducible try to take several thread dumps with delay
about 15s.
I saw you use the cvs filesystem. Try the same with plain local
filesystem.

It would be also helpful if you could widen your console to not break
lines. Thanks
Comment 6 isullivan 2004-02-24 20:09:39 UTC 
Yes, the CPU was "free" (normal background usage) when I took the 
second thread dump.

As I noted orignally this is not easily reproducable, it's happened 
one more time since I reported it so that's twice out of maybe 100 
debugging sessions. The next time it happens I will try to take the 
thread dumps.

Sorry I don't have any more info.
Comment 7 Martin Matula 2004-07-28 13:12:04 UTC 
The code in the thread dumps is rewritten so it should no longer
happen. Please reopen if this occurs again and provide a more recent
thread dumps.