Community
Participate
Working Groups
Steps: 1. Open BugzillaSearchPage from Mylyn code base 2. Type GridData 3. Press Ctrl+Space 4. Press Enter Eclipse crashes with a Gtk error (see below). Environment: Ubuntu/lucid beta 2, libgtk2 2.20.0-0ubuntu4 eclipse.buildId=I20100312-1448 java.version=1.6.0_19 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_CA Framework arguments: -keyring /home/stp/.eclipsekeyring Command-line arguments: -os linux -ws gtk -arch x86 -data /home/stp/.workspace -keyring /home/stp/.eclipsekeyring Console output: The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 218096 error_code 158 request_code 148 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Please see bug 303372.
Thanks Remy. I was able to work around the crash by installing xulrunner-1.9.2 and starting eclipse with -vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/bin/xulrunner (not sure if that's really necessary).
(In reply to comment #2) > Thanks Remy. I was able to work around the crash by installing xulrunner-1.9.2 > and starting eclipse with -vmargs > -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/bin/xulrunner (not sure if that's > really necessary). I confirm that the Steffen's solution works for me and it is necessary to set the property "-Dorg.eclipse.swt.browser.XULRunnerPath". I set: -vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/bin/xulrunner-1.9.2 in my eclipse.ini Thanks bye
*** Bug 319271 has been marked as a duplicate of this bug. ***
I had such a problem, my Eclipse started crashing with RenderBadPicture too. Eclipse crashed always when internal webbrowser painted some image and closed window (or sub-windows) with it. The simple way of reproducing this crash: - start eclipse - menu / help / Help Contents - close window with eclipse helps - crash after closing help window W/o images internal webbrowser works perfectly. I used strace for analysing the matter of crashing. The difference between working and crashing version of eclipse was conclused in following: crashed version was trying to load /usr/lib/xulrunner-devel-1.9.1.11 and /usr/lib/xulrunner-1.9.1.11 despite that `/usr/bin/xulrunner --gre-version` = 1.9.2.8 was installed. After deinstalling xulrunner-1.9.1.11 with remaining xulrunner-1.9.2.8 Eclipse works perfectly. Hope this helps someone.
Thank you, Ivanov, it did help me. I had plenty of - JVM terminated Exit code=1 - JVM terminated Exit code=13 on 64-bit Ubuntu 10.10 using openjdk 6 helped a little bit For the crash in this ticket, the X output is swallowed by the launcher. I started eclipse, then verified what the jvm command was, launched that command line and got to see the output <have eclipse running> foxyboy@c505:~$ ps -ef | grep eclipse foxyboy 15496 1 0 22:29 ? 00:00:00 /opt/eclipse/eclipse -vm /usr/lib/jvm/java-6-openjdk/bin -vmargs -XX:MaxPermSize=256m foxyboy 15497 15496 34 22:29 ? 00:00:26 /usr/lib/jvm/java-6-openjdk/bin/java -XX:MaxPermSize=256m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1.R36x_v20100810/eclipse_1309.so -startup /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -exitdata 2fce0022 -vm /usr/lib/jvm/java-6-openjdk/bin/java -vmargs -XX:MaxPermSize=256m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar foxyboy 15584 15497 0 22:29 ? 00:00:00 /usr/bin/python2.6 -u /opt/eclipse/plugins/org.python.pydev_1.6.3.2010100513/PySrc/pycompletionserver.py 33940 47636 foxyboy 15768 31310 0 22:30 pts/2 00:00:00 grep eclipse exit eclipse, then execute the listed jvm command, run to crash: foxyboy@c505:~$ /usr/lib/jvm/java-6-openjdk/bin/java -XX:MaxPermSize=256m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1.R36x_v20100810/eclipse_1309.so -startup /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -exitdata 2fbc8016 -vm /usr/lib/jvm/java-6-openjdk/bin/java -vmargs -XX:MaxPermSize=256m -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar Xlib: extension "RANDR" missing on display ":0.0". 2010-12-01 22:23:55.773:INFO::Logging to STDERR via org.mortbay.log.StdErrLog 2010-12-01 22:23:55.789:INFO::jetty-6.1.x 2010-12-01 22:23:55.823:INFO::Started SocketConnector@0.0.0.0:50313 The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 47078 error_code 174 request_code 152 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)