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 220855 - 100% CPU usage in IDE after unit tests are finished on Maven project
Summary: 100% CPU usage in IDE after unit tests are finished on Maven project
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 7.3
Hardware: PC Other
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
: 221012 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-10-25 15:11 UTC by NukemBy
Modified: 2012-11-01 09:57 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Self Sampler snapshot (15.87 KB, application/octet-stream)
2012-10-25 15:11 UTC, NukemBy 		Details
Screen shot of the back trace having most of self time (203.72 KB, image/jpeg)
2012-10-25 15:13 UTC, NukemBy 		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 NukemBy 2012-10-25 15:11:47 UTC 
Created attachment 126556 [details]
Self Sampler snapshot

I have a problem with Netbeans IDE which most probably appeared around 2 weeks ago in Dev build. Currently i'm running version of Netbeans built from rev 244450.

The problem is - task manager on my Win Srv 2003 shows constant 25% CPU usage of Netbeans after i have executed unit tests on my Maven project at least once. 25% is 100% of one of 4 cores on my CPU. This most probably means there is some low-priory thread constantly doing something (thread is low-priority - because I do not notice any lags in user experience or other operations).

I'm attaching self sampler reports and screenshot of the back trace having most of the self time.
Comment 1 NukemBy 2012-10-25 15:13:07 UTC 
Created attachment 126558 [details]
Screen shot of the back trace having most of self time
Comment 2 Tomas Hurka 2012-11-01 08:51:20 UTC 
Unfortunately the snapshot does not give a clue, what is going on. There is nothing suspicious, except the fact that  Are you able to reproduce it?  Can you provide exact steps, how to reproduce it? Thanks.
Comment 3 Tomas Hurka 2012-11-01 09:11:39 UTC 
(In reply to comment #2)
> Unfortunately the snapshot does not give a clue, what is going on. There is
> nothing suspicious, except the fact that  
... java.lang.Throwable.getStackTraceElement[native]() is taking a long time.
Comment 4 Petr Cyhelsky 2012-11-01 09:22:54 UTC 
*** Bug 221012 has been marked as a duplicate of this bug. ***
Comment 5 Tomas Hurka 2012-11-01 09:57:57 UTC 
The problem with java.lang.Throwable.getStackTraceElement should be fixed by:

changeset   : 237848:6a04259e1d80
author      : Jaroslav Tulach <jtulach@netbeans.org>
date        : Thu Nov 01 10:25:32 CET 2012
summary     : #192886: Really don't collect stacktraces