Why does my Eclipse Luna 4.4 crash on Debian Wheezy 7.4 with Oracle JDK8 64bit?
Solution 1
According to: https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736
Add to 2 lines eclipse.ini:
--launcher.GTK_version
2
The option --launcher.GTK_version should be before --launcher.appendVmargs
Problem (dialogs does not work properly) with TIBCO Jaspersoft® Studio - Visual Designer for JasperReports:
edit Jaspersoft Studio.ini like this:
-startup
plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.GTK_version
2
--launcher.library
Or add this before start Jasper Studio (runubuntu.sh):
export SWT_GTK3=0
Solution 2
I found this solution at eclipse bugs page
export SWT_GTK3=0
Solution 3
try to edit your eclipse.ini file like this:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
Solution 4
I had the same problem with Eclipse based Sping Tool Suite (STS) and JDK 8 when launching STS on Debian Wheezy 7.6 64-bit. Adding those two lines, as suggested by other answers, to the init file sts.ini (eclipse.ini) did the work.
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326
-product
org.springsource.sts.ide
--launcher.defaultAction
openFile
--launcher.GTK_version
2
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
Solution 5
On Debian Wheezy 7.8 (64bit) & using Eclipse - Luna 4.4.2. Comments by harshrc on Bug 430736 were the most relevant in my case and resolved crash post splash screen. Launch eclipse with export SWT_GTK3=0
# from CLI / prompt in eclipse folder:
export SWT_GTK3=0 ; ./eclipse
domandinho
I have over 6 years of experience as a Python Developer. I’ve graduated from the Faculty of Mathematics, Informatics, and Mechanics of the University of Warsaw with a Master's Degree in Computer Science. I am interested especially in big data processing and cloud computing. I love reading professional literature, watching tech talks, and learning new things. I have many ideas on how to improve software and realize many of them in my free time. I also like to help other less experienced developers by resolving their problems and answering their questions on stack overflow or in my job. I am also an open-source enthusiast. I’ve contributed to projects such as Django, Google PyType, AWS CLI, and many other open-source projects.
Updated on February 01, 2020Comments
-
domandinho over 4 years
I have Debian GNU/Linux 7.4 (wheezy) OS installed on Oracle VirtualBox and:
java version "1.8.0_11" Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)I downloaded Eclipse Luna 4.4. When I was trying to run Eclipse an error occurred:
A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007f9e8a42173f, pid=10942, tid=140319582553856 JRE version: Java(TM) SE Runtime Environment (8.0_11-b12) (build 1.8.0_11-b12) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops) Problematic frame: C [libgdk-x11-2.0.so.0+0x5173f] gdk_display_open+0x3f Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting JavaSo I issued a command in the terminal:
$ ulimit -c unlimited $ ./eclipseBut the next error occurred:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 (java:11276): GLib-GObject-WARNING **: cannot register existing type `GdkDisplayManager' (java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (java:11276): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (java:11276): GLib-GObject-WARNING **: invalid (NULL) pointer instance (java:11276): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (java:11276): GLib-GObject-WARNING **: invalid (NULL) pointer instance (java:11276): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (java:11276): GLib-GObject-WARNING **: cannot register existing type `GdkDisplay' (java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (java:11276): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed (java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (java:11276): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007f216d28473f, pid=11276, tid=139782222493440JRE version: Java(TM) SE Runtime Environment(8.0_11-b12) (build 1.8.0_11-b12) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops) Problematic frame: C [libgdk-x11-2.0.so.0+0x5173f] gdk_display_open+0x3f Core dump written. Default location: /home/abcdef/ECLIPSE_JAVA/eclipse/core or core.11276
I also tried to solve this problem by adding:
-Dorg.eclipse.swt.browser.DefaultType=mozillato eclipse.ini, but it didn't help.
Can anybody help me with this problem?