Community
Participate
Working Groups
Created attachment 104110 [details] It contains 37 Eclipse generated log files. Build ID: I20070625-1500 Steps To Reproduce: 1. Develop something in CDT (I'm not sure if it a CDT-specific bug) 2. Save. Modify something and save again and again. 3. Eclipse will quit and left a log in my home folder. I'll attach 37 (!) .log files. I hope, those will help you. More information: I'm on openSUSE 11. uname -a: Linux 2.6.25.4-10-pae #1 SMP java -version: java version "1.6.0_06" Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) Server VM (build 10.0-b22, mixed mode)
Could you please try to launch Eclipse with another JVM? Your crash logs indicate that the JVM used is Java VM: OpenJDK Server VM (1.6.0-b09 mixed mode linux-x86) (icedtea).
I went through a few of these, sounds like a duplicate of everyone's favourite bug 214092.
As the comments in the fixed bug recommended, I add the following two lines into eclipse.ini: -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init> But Eclipse freezes as it did before. I don't know exactly whether the fix has a connection between these two lines but if it relies on these, it doesn't work, I'm afraid of. So maybe isn't it a duplicate?
(In reply to comment #3) > But Eclipse freezes as it did before. You did not mention Eclipse ever freezing in your original comment. You only noted that Eclipse crashed. When does it freeze? Is it consistently reproducible?
I'm sorry, I meant Eclipse crashes, not freezes. After a crash it shows a dialogue with these parameters: JVM terminated. Exit code=1 /usr/lib/jvm/java-1.6.0-sun-1.6.0.u6/jre/bin/java -jar /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -os linux -ws gtk -arch x86 -showsplash -launcher /usr/lib/eclipse/eclipse -name Eclipse --launcher.library /usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.0.v20070606/eclipse_1017a.so -startup /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -exitdata 18b8007 -vm /usr/lib/jvm/java-1.6.0-sun-1.6.0.u6/jre/bin/java -vmargs -jar /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar It doesn't contain the 2 "-XX:CompileCommand=" lines (don't know if it is an error).
(In reply to comment #5) > It doesn't contain the 2 "-XX:CompileCommand=" lines (don't know if it is an > error). You want those lines _after_ the -vm argument in the eclipse.ini. Also taking care that it has to be on its own line. Alternatively, I could also suggest trying to start Eclipse with a Java 5 JRE. That should also prevent this bug as it is a problem with the Java 6 line.
Remy, is there a reason you made this bug viewable by committers only?
(In reply to comment #7) > Remy, is there a reason you made this bug viewable by committers only? I think I might've been tabbing around and accidentally hit the space bar while focus was on the checkbox or I might've clicked it by mistake. No, this was not intentional. Please remove it if you agree that there is no reason for this to be hidden, John.
(In reply to comment #6) > You want those lines _after_ the -vm argument in the eclipse.ini. Also taking > care that it has to be on its own line. Alternatively, I could also suggest > trying to start Eclipse with a Java 5 JRE. That should also prevent this bug as > it is a problem with the Java 6 line. Sorry, this should be _after_ the -vmargs argument. Are you following the sample config file in bug 214092 comment 13?
Remy, did you intend to check the security advisory box? Or am I missing something here that makes this a security issue?
(In reply to comment #10) > Remy, did you intend to check the security advisory box? Or am I missing > something here that makes this a security issue? > Sorry :) I should have refreshed the bug to see this asked and answered.
Created attachment 104835 [details] Eclipse crash log file with Java 1.7.0 I installed the newest Java: java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea Server VM (build 1.7.0-b24, mixed mode) But nothing changed. I'll attach the generated log file.
(In reply to comment #12) > Created an attachment (id=104835) [details] > Eclipse crash log file with Java 1.7.0 > > I installed the newest Java: > java version "1.7.0" > IcedTea Runtime Environment (build 1.7.0-b24) > IcedTea Server VM (build 1.7.0-b24, mixed mode) > > But nothing changed. > I'll attach the generated log file. I see two potential problems here, a) this is an IcedTea problem and you need to talk to them about this or b) your edited eclipse.ini is incorrect for whatever reasons. I strongly recommend you try to run Eclipse with Java 5 from Sun (which will _not_ require the -XX workarounds) and see the behaviour of that.
I switched the JVM (update-alternatives --config java) to /usr/lib/jvm/jre-1.5.0-sun/bin/java, but in that case Eclipse doesn't want to start. It crashes with the following: JVM terminated. Exit code=1 /usr/lib/jvm/java-1.5.0-sun-1.5.0_update15/jre/bin/java -jar /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -os linux -ws gtk -arch x86 -showsplash -launcher /usr/lib/eclipse/eclipse -name Eclipse --launcher.library /usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.0.v20070606/eclipse_1017a.so -startup /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -exitdata 307800a -vm /usr/lib/jvm/java-1.5.0-sun-1.5.0_update15/jre/bin/java -vmargs -jar /usr/share/eclipse/./plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar Then I'd switched back to JVM 1.7.0 and deleted /usr/share/eclipse/eclipse.ini (with all of hack in it). After a short usage Eclipse crashed. To sum up, with 1.5.0 Eclipse doesn't start and both with 1.6.0 and 1.7.0 it crashes.
/usr/share? /usr/lib? Are you on Ubuntu? Are you using Ubuntu's eclipse builds?
As you(In reply to comment #15) > /usr/share? /usr/lib? Are you on Ubuntu? Are you using Ubuntu's eclipse builds? > As you can see from my first comment (and from the end of the log files) I'm on openSUSE 11. Yes, I'm using the following rpm-s: eclipse-3.3-150 eclipse-archdep-platform-commons-3.3-143 eclipse-archdep-gtk2-3.3-143 eclipse-archdep-scripts-3.3-143 eclipse-archdep-platform-3.3-143
(In reply to comment #16) > As you can see from my first comment (and from the end of the log files) I'm on > openSUSE 11. > Yes, I'm using the following rpm-s: > eclipse-3.3-150 > eclipse-archdep-platform-commons-3.3-143 > eclipse-archdep-gtk2-3.3-143 > eclipse-archdep-scripts-3.3-143 > eclipse-archdep-platform-3.3-143 Sorry about that. Anyway, can you please try using an Eclipse build from eclipse.org? Please try 3.3.2 or 3.4RC4, thanks. http://download.eclipse.org/eclipse/downloads/
I downloaded Eclipse 3.4.0 RC4 (newer is better for me :), and CDT 5.0.0. Then I opened my project and saved it a lot of times. Tried to insert and delete lines then save again but nothing special happened :] So, I couldn't make Eclipse crash, neither with JVM 1.6.0 and 1.7.0! And I feel it a bit faster, so I like it. Thank you for the tip.
(In reply to comment #18) > I downloaded Eclipse 3.4.0 RC4 (newer is better for me :), and CDT 5.0.0. > Then I opened my project and saved it a lot of times. Tried to insert and > delete lines then save again but nothing special happened :] > > So, I couldn't make Eclipse crash, neither with JVM 1.6.0 and 1.7.0! That's odd, did you change the eclipse.ini file to add the workaround? Technically, it should still be crashing on Java 6. I suggest you file a bug to the SuSE team as I am sure they would like to investigate the crashes.
No, I didn't change anything in the .ini file. I've reported this bug to the Novell team: https://bugzilla.novell.com/show_bug.cgi?id=400366 I hope, they track down what was the error.
Closing as VM error.
