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 183621

Summary: [69cat] [ide] CPU near 100% after long period of operation
Product: ide Reporter: esmithbss <esmithbss>
Component: PerformanceAssignee: issues@performance <issues>
Status: CLOSED DUPLICATE    
Severity: normal    
Priority: P3    
Version: 3.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: Snapshot 1
Snapshot 2
Snapshot 3
Snapshot 4
Snapshot 5
Snapshot 6 -- Normal IDE Behavior following restart of NetBeans.

Description esmithbss 2010-04-07 06:19:58 UTC
[ BUILD # : 201004060201 ]
[ JDK VERSION : 1.6.* ]

After I've been using NetBeans for an extended period of time (multiple hours)
and having run multiple debug sessions, NetBeans starts hitting 100% on my
CPUs.  The only way to get back to a performant system is to shut the IDE down
and restart it.

I've attached multiple snapshots (*.nps) taken over multiple minutes of a
single run for this issue.
Comment 1 esmithbss 2010-04-07 06:20:52 UTC
Created attachment 96836 [details]
Snapshot 1
Comment 2 esmithbss 2010-04-07 06:21:34 UTC
Created attachment 96837 [details]
Snapshot 2
Comment 3 esmithbss 2010-04-07 06:22:29 UTC
Created attachment 96838 [details]
Snapshot 3
Comment 4 esmithbss 2010-04-07 06:22:57 UTC
Created attachment 96839 [details]
Snapshot 4
Comment 5 esmithbss 2010-04-07 06:23:28 UTC
Created attachment 96840 [details]
Snapshot 5
Comment 6 esmithbss 2010-04-07 06:25:08 UTC
Created attachment 96841 [details]
Snapshot 6 -- Normal IDE Behavior following restart of NetBeans.
Comment 7 Peter Pis 2010-04-07 08:17:34 UTC

*** This bug has been marked as a duplicate of bug 183201 ***
Comment 8 esmithbss 2010-04-07 14:40:08 UTC
183201 is marked as Resolved Fixed with the patches in 201004060201.

This issue appeared in 20104060201 so either we have a new issue, or the fix for 183201 has a new edge condition that isn't being taken care of.

Marking as Reopened for more evaluation.
Comment 9 Peter Pis 2010-04-10 16:38:34 UTC

*** This bug has been marked as a duplicate of bug 183201 ***