Red Hat Bugzilla – Bug 209031
eclipse 3.1.2 consumes all memory
Last modified: 2007-11-30 17:11:45 EST
Description of problem:
starting eclipse consumes all available RAM an slows a machine down until killed
Version-Release number of selected component (if applicable):
Not it is random as far as observed
Steps to Reproduce:
1. Start eclipse
classes are loaded to a random point and then RAM is consumed, eclipse no longer
responds, and the process must be killed (which is difficult with a nearly
I have had this with various plugins installed phpeclipse, pydev, wst/wtp
What architecture are you using?
I had this problem on one of my i386 machines as well but it seemed to be
machine dependent because another box I had didn't have this problem.
Are you planning to upgrade to FC6? If so, I'd like to know how things go with
that release. If it's still broken in FC6, I'll track down the machine that had
the problem with FC5 and see if I can reproduce it as well. Thanks.
Just downloaded FC6-pre DVD ISO images. Did an upgrade. Had a few package
problems (I had the livna repo enabled previously and X wouldn't start because I
had the nvidia driver installed as well). Once I got all that cleaned up. Logged
in. Started a few apps (evolution,gaim,banshee). Then started eclipse. First
time start, and it started to eat ram. It ended up consuming 1GB of physical ram
and 1G of swap before I finally killed it, I say finally because machine
response was obviously very slow.
I've done a clean re-install of eclipse about 3 times, removing it and all
dependancies, eclipse-*, ant, tomcat libswt3-gtk, rm -rf /usr/share/eclipse. I
have a couple plugins installed phpeclipse, phpide and pydev, plus their
dependancies. I haven't been using eclipse much of late the last few days.
Tonight I was going to start a python project. Starting ecplise started to
consume all the memory again. Is there anyway I can strace it or something to
provide more info? I'm not so well versed with tracing java issues. Just let me
This is really a GCJ problem. Tom Fitzsimmons said he would help you get started
profiling this. Thanks Tom.
Nathanael, install the gcc-debuginfo package using yum. Then you can use
oprofile to collect and display profiling data.
First run eclipse as you normally would. Then as root, run:
opcontrol --start --no-vmlinux
wait a minute or so, then run:
and post the result of:
here. You may need to install the debuginfo from other relevant packages too,
but you don't need to recollect the profiling data again; installing more
debuginfo will only make the opreport output more meaningful.
Is this to be done when there is a problem, or when it is working correctly?
When there is a problem.
FC5 is no longer supported and the requested oprofile data hasn't been supplied
either. If you can reproduce this in F7 or on rawhide, please reopen with
the requested data.