Bug 167548 - CPU Load sits at 100% when using eclipse in java perspective
Summary: CPU Load sits at 100% when using eclipse in java perspective
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 4
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-05 05:29 UTC by Daniel Draper
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-05 20:43:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Draper 2005-09-05 05:29:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

Description of problem:
Switching to Java perspective and opening a Java file causes severe system slow down and java process uses 100% of CPU. Compilation is very slow and throws errors such as "Error cleaning output folder".

I am using separate source and output folders and I have two JRE's installed - the standard ECJ that comes with FC4 and j2sdk-1.4.2_09. The latter is currently set as my default jre.

I try removing ~/.eclipse but this has no effect except to switch me back to resource perspective. I am experiencing frequent crashes as well.

I have extra installed plugin: a javascript plugin from sourceforge and includes the following:
net.sf.wdte.core_0.0.9                          
net.sf.wdte.js.core_0.0.9
net.sf.wdte.js.ui_0.0.9
net.sf.wdte.ui_0.0.9


Version-Release number of selected component (if applicable):
eclipse-ecj-3.1.0_fc-0.M6.22
eclipse-jdt-3.1.0_fc-0.M6.22
eclipse-bugzilla-0.1.0_fc-16
eclipse-pydev-0.9.3_fc-7
eclipse-cdt-3.0.0_fc-0.M6.7
eclipse-changelog-2.0.1_fc-21
eclipse-platform-3.1.0_fc-0.M6.22

How reproducible:
Always

Steps to Reproduce:
1.Open eclipse
2.switch to java perspective
3.open java file and edit
  

Actual Results:  CPU Load very high. Java process using lots of CPU. Compilation slow.

Expected Results:  I would expect minimal overhead.

Additional info:

Comment 1 Andrew Overholt 2005-11-01 19:34:54 UTC
I can't reproduce this.  If this is a Sun JVM issue, I can't really help you. 
Have you tried upstream Eclipse downloads to see if it is duplicatable there?

Comment 2 Billy Biggs 2005-11-01 19:42:40 UTC
You can get a stack trace from the Sun JVM by sending a SIGQUIT.
Use "kill -3 <pid>" where <pid> is the PID of the Java process.  This
may be able to give you hints about where the problem may be.

Comment 3 John Thacker 2006-05-05 20:43:08 UTC
Closing due to lack of response from reporter.


Note You need to log in before you can comment on or make changes to this bug.