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 56483 - [perf] 100% CPU browsing through JDK classes
Summary: [perf] 100% CPU browsing through JDK classes
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: _ rkubacki
URL:
Keywords: JDK_SPECIFIC, PERFORMANCE, RANDOM
: 57065 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-15 18:05 UTC by Jesse Glick
Modified: 2008-12-22 17:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Some thread dumps taken at random over the course of a few minutes (138.81 KB, text/plain)
2005-03-15 18:06 UTC, Jesse Glick 		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 Jesse Glick 2005-03-15 18:05:23 UTC 
Second or third time this has happened to me recently, though I am not sure what
I was doing last time. JDK 1.6.0, recent dev build.

Was just jumping through some Ant stack trace lines going through JDK classes.
Fine for a couple of lines, then I jumped into one class and the file opened but
the caret did not move. Then the CPU usage went to 100% and the screen froze.
Stayed that way for several minutes while I took thread dumps. Could eventually
close IDE by clicking the close button on the window (took about a minute to
respond).

Just guessing at the component here.
Comment 1 Jesse Glick 2005-03-15 18:06:11 UTC 
Created attachment 20858 [details]
Some thread dumps taken at random over the course of a few minutes
Comment 2 Martin Matula 2005-03-16 21:25:13 UTC 
I've seen a very similar thing when I disabled and enabled a module in NetBeans
for about 3 times. It is reliably reproducible (I didn't get further than 3 or 4
times enabling and disabling). The CPU goes to 100%, thread dumps do not show
any heavy activity. 
I doubt it has anything to do with the javacore module. I suspect there is
something happening in the VM based on the fact the IDE is spending so much time
(based on the number of thread dumps) in a trivial method like
org.netbeans.jmi.javamodel.JavaClass$Impl.getModifiers(Unknown Source).
Maybe the VM goes low on the perm. area and tries to free it or something like that.
Comment 3 Jan Becicka 2005-03-24 13:25:07 UTC 
It looks like general problem of whole IDE. Perf. guys, please evaluate. Thanks.
Comment 4 Jan Becicka 2005-03-29 06:13:08 UTC 
*** Issue 57065 has been marked as a duplicate of this issue. ***
Comment 5 _ rkubacki 2005-03-30 20:19:27 UTC 
It seems to me that XAWT toolkit behaves badly. AFAIK this is something what is
new in mustang builds so it can be related. 

To Martin: there was some perf problem with growing number of listeners when you
disabled/enabled module in recent builds but this should be fixed. Petr N. knows
details.
Comment 6 Petr Nejedly 2005-03-31 08:33:38 UTC 
To Martin: It was issue 56375, but it is completly unrelated to this one...
Comment 7 Roman Strobl 2005-06-13 11:47:37 UTC 
Can this issue be assigned to a component? To keep the IDE issues clean... thanks.
Comment 8 _ rkubacki 2006-01-11 19:35:36 UTC 
Jesse, is this still a problem? I do not see it on my machine.
Comment 9 Jesse Glick 2006-01-11 23:07:55 UTC 
Don't think I've seen this happen in a while.
Comment 10 Marian Mirilovic 2006-01-12 10:20:25 UTC 
verified