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 241833 - Netbeans 8 needs a lot of CPU time when idle
Summary: Netbeans 8 needs a lot of CPU time when idle
Status: NEW
Alias: None
Product: third-party
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: toomasr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-13 16:07 UTC by tomzi
Modified: 2018-03-23 09:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
.npss file attached from NetBeans (106.02 KB, application/x-npss)
2014-02-13 16:07 UTC, tomzi 		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 tomzi 2014-02-13 16:07:19 UTC 
CPU is around 50% on  a dual core when nothing is happing - no compilation...

Product Version = NetBeans IDE 8.0 Beta (Build 201401141042)
Operating System = Linux version 3.5.0-45-generic running on amd64
Java; VM; Vendor = 1.7.0_51
Runtime = Java HotSpot(TM) 64-Bit Server VM 24.51-b03
Comment 1 tomzi 2014-02-13 16:07:46 UTC 
Created attachment 145156 [details]
.npss file attached from NetBeans

.npss file
Comment 2 Ondrej Vrabec 2014-02-14 08:11:34 UTC 
the only running thread is org.zeroturnaround.jrebel.netbeans.patcher.Patcher.tryPatch()	83.17394	11 894 ms (83,2%)	11 894 ms
playing with jar files
Comment 3 tomzi 2014-02-18 07:37:30 UTC 
You are right, I deactivated jrebel just to it out and netbeans is nice and quiet now :) Is there any way to tell the jrebel guys that...?
Comment 4 tomzi 2014-02-18 07:38:51 UTC 
The jrebel plugin version I have is 1.5.9
Comment 5 marco.marsala 2018-03-23 09:11:51 UTC 
CPU usage is 100% 1-core when any .php file is just opened in Netbeans IDE (and its tab is focused).

This happens with small files too, I mean under than 2000 lines.

After closing all files the CPU usage immediately returns to 0%.