Community
Participate
Working Groups
When I launch Eclipse, cpu usage goes up to 99% and never drops. When I change to other perspectives it drops to 0%, but when changed back to Java perspective it goes up again. Normally it would drop to 0% after I change perspectives repeatedly. I'm using GTK2 version of Eclipse on RedHat beta(phoebe)/GNOME 2.2. Could you fix this problem please? Thanks.
Can you attach a java dump file from the time when the cpu is busy? You can capture this with "kill -3 <pid>" where <pid> is the process of the java VM. Without a trace we have no idea where the time is going.
Created attachment 4484 [details] Stacktrace of java process
Seems to be spinning the event loop. Moving to SWT for futher investigation. I noticed you're running on Blackdown... it would be interesting to know if you get the same behaviour with a Sun or IBM VM.
I haven't tested with IBM's but have exprienced the same lock ups with Sun's JVM. However, those lock ups seem to change from version to version(or time to time) since somethimes it makes IDE completely unusable, and other times it only eats up CPU cycles.
I have the same problem using sun jdk or ibm jdk. When in java view sometimes eclipse just use 100% cpu and never stops until i change view. stop times it just makes eclipse unusable and i kill it.
Which version of Eclipse are you running ? Please also look: Bug#31525, it talks about a bug in GTK in the beta RedHat (phoebe). Bug#36191, is bug about antialiasing, the description of this bug is similar to yours.
FH is tracking this.
I get similar behavior using the PHP-Eclipse plugin on Mandrake 9.1 with j2re 1.4.1. I'm using Eclipse-gtk 2.1. After Eclipse starts, the processor sits at 99% until I change perspectives and then change back.
Created attachment 4597 [details] Eclipse stack trace Same problem here with Mandrake 9.1 and Eclipse 2.1 and RC2. Did not have the problem with RC2 on Mandrake 9.0. Problem occurs in two cases: 1) if I try to create a new text file, right clicking on a folder in Package Explorer. Hitting "finish" does it. Does not happen if I invoke "File | New | File" from the main menu. 2) Sometimes, after changing preferences, the next time eclipse is started, it may load and then enter this heavy cpu usage state. Killing eclipse and renaming the "workspace" folder solves the problem, returning the folder back causes the problem again. Someting in the setting does it, but have been unable to detect so far. When this happens, the java main thread takes ~50% and the X process takes the other ~50%. In both cases for me Eclipse is unusable and the only way out is kill. Including stacktrace for case (1), it is basically the same as the one attached before.
Xavier: This problem is likely caused by a bug in GTK, the fix is to update to Redhat 9.0. If you don't want to update your whole system will need at least update the gtk libs. gtk-2.2.1-1 (which is part to redhat phoebe) has the bug gtk-2.2.1-4 (which is part to redhat 9.0) does not have the bug Please, see bug#36698
*** Bug 35872 has been marked as a duplicate of this bug. ***
*** Bug 36677 has been marked as a duplicate of this bug. ***
Felipe, How would I fix this under Windows? Is GTK used here as well? I observe the same behaviour as described by Dave in comment #9.
Marcus: This problem is GTK specific and I don't know how to fix it for Windows, you would need to enter a problem report against Component SWT, OS Windows. Although you see the same behavior the cause of the problem has to be completely different.
*** Bug 36925 has been marked as a duplicate of this bug. ***
Xavier, are you still having this problem ? can I close this bug ? let me know okay. thanks
I had this problem with SuSE 8.2 which has gtk 2.2.1-29. I compiled a GTK+ from the current CVS (May 18th 2003) and the problem has gone away.
*** This bug has been marked as a duplicate of 36698 ***
