Eclipse crashes very often because of problems with GTK

Starting a freshly downloaded Eclipse Luna fails. Error log attached.

Tried Java and Java EE versions (both fail with the same error).

Created attachment 241028
Error log produced by Eclipse at startup.

Comment on attachment 241028
Error log produced by Eclipse at startup.

Configured Sun Java 8 via -vm in eclipse.ini (but it also fails with the same error when using default OpenJDK 7 - hence no -vm specified in eclipse.ini ).

This is a very unusual crash during the initial load of GTK+ itself. Which versions of GTK+ 2 and GTK+ 3 are installed on this machine?

Its possible that this is an issue caused by the oxygen GTK theme that KDE uses. Can you please try the workaround mentioned here - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/comments/51 - and update whether it resolves the crash?

(In reply to Arun Thondapu from comment #3)
> This is a very unusual crash during the initial load of GTK+ itself. Which
> versions of GTK+ 2 and GTK+ 3 are installed on this machine?

Default Debian 7.4 Wheezy install via text installer on DVD with additional packages installed. The output of a grep of gtk related packages is given below:

# dpkg -l '*gtk*' | grep ^i
ii libcanberra-gtk3-0:amd64 0.28-6 amd64 GTK+ 3.0 helper for playing widget event sounds with libcanberra
ii libcanberra-gtk3-module:amd64 0.28-6 amd64 translates GTK3 widgets signals to event sounds
ii libgpod4-nogtk:amd64 0.8.2-7 amd64 library to read and write songs to an iPod
ii libgtk-3-0:amd64 3.4.2-7 amd64 GTK+ graphical user interface library
ii libgtk-3-bin 3.4.2-7 amd64 programs for the GTK+ graphical user interface library
ii libgtk-3-common 3.4.2-7 all common files for the GTK+ graphical user interface library
ii libgtk2.0-0:amd64 2.24.10-2 amd64 GTK+ graphical user interface library
ii libgtk2.0-bin 2.24.10-2 amd64 programs for the GTK+ graphical user interface library
ii libgtk2.0-common 2.24.10-2 all common files for the GTK+ graphical user interface library
ii libgtkmm-2.4-1c2a 1:2.24.2-1 amd64 C++ wrappers for GTK+ (shared libraries)
ii libjavascriptcoregtk-1.0-0 1.8.1-3.4 amd64 Javascript engine library for GTK+
ii libwebkitgtk-1.0-0 1.8.1-3.4 amd64 Web content engine library for GTK+
ii libwebkitgtk-1.0-common 1.8.1-3.4 all Web content engine library for GTK+ - data files
ii libwxgtk2.8-0:amd64 2.8.12.1-12 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
ii pinentry-gtk2 0.8.1-1 amd64 GTK+-2-based PIN or pass-phrase entry dialog for GnuPG
ii python-gtk2 2.24.0-3+b1 amd64 Python bindings for the GTK+ widget set

> Its possible that this is an issue caused by the oxygen GTK theme that KDE
> uses. Can you please try the workaround mentioned here -
> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/comments/51 -
> and update whether it resolves the crash?

I don't have the GTK tab or option under System Settings -> Application Appearance

Do remember this from earlier KDE use so I'll try to find out why it's not there. Will try install of gtk3-engines-oxygen kde-config-gtk-style-preview packages, which are not installed on my system (should they be?).

Created attachment 241184
GTK configuration for KDE

(In reply to Arun Thondapu from comment #3)
> Its possible that this is an issue caused by the oxygen GTK theme that KDE
> uses. Can you please try the workaround mentioned here -
> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/comments/51 -
> and update whether it resolves the crash?

Installed kde-config-gtk-style to get the GTK Configuration (screendump attached)
and set to Raleigh.

No difference, it still crashes but now with a different error message:

$ ./eclipse
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.

(java:7456): GLib-GObject-WARNING **: cannot register existing type `GdkDisplayManager'

(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:7456): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

(java:7456): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(java:7456): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(java:7456): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(java:7456): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(java:7456): GLib-GObject-WARNING **: cannot register existing type `GdkDisplay'

(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:7456): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed

(java:7456): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:7456): 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=0x00007fe97938573f, pid=7456, tid=140641328412416
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 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 Java again
#
# An error report file with more information is saved as:
# /home/mdo/Downloads/Eclipse/4.4 (Luna)/eclipse/hs_err_pid7456.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

BTW: Eclipse Kepler with Java8 update patch works fine.

Hi,

According to the log we can see that both GTK2 and GTK3 libraries are loaded and the gtk2 pi library loaded.

In luna eclipse should have started with GTK3 and GTK3 PI libraries by default. Can you please let us know about the following

1. If there are any environment settings done before starting eclipse ?
2. Is this problem reproducible with Java 7?

Thanks
Sravan

Also

Can please please try using a new workspace?

Please provide us the build id this can be obtained from help->about eclipse

Thanks
Sravan

(In reply to Sravan Kumar Lakkimsetti from comment #8)
> Hi,
>
> According to the log we can see that both GTK2 and GTK3 libraries are loaded
> and the gtk2 pi library loaded.
>
> In luna eclipse should have started with GTK3 and GTK3 PI libraries by
> default. Can you please let us know about the following
>
> 1. If there are any environment settings done before starting eclipse ?
> 2. Is this problem reproducible with Java 7?
>
> Thanks
> Sravan

1. tried running it from a clean account (so no specific environment variables and also no workspace yet) and it still crashes

2. env. vars.: see 1. above; tried openjre7 from Debian respository, Luna also crashes, see log below.

3. build version: I cannot determine this from the Eclipse GUI Help->About because it crashes before the GUI is activated (I only see the small startup flash window).

$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

mdo@vapulo:~/Downloads/Eclipse/4.4 (Luna)/eclipse$ ./eclipse
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.

(java:15330): GLib-GObject-WARNING **: cannot register existing type `GdkDisplayManager'

(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:15330): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

(java:15330): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(java:15330): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(java:15330): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(java:15330): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(java:15330): GLib-GObject-WARNING **: cannot register existing type `GdkDisplay'

(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:15330): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed

(java:15330): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(java:15330): 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=0x00007f5db090c73f, pid=15330, tid=140040758400768
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 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 Java again
#
# An error report file with more information is saved as:
# /home/mdo/Downloads/Eclipse/4.4 (Luna)/eclipse/hs_err_pid15330.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Ma...

Found this bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=420180

but setting environment variable SWT_GTK3 to 1 does not make a difference.

Have install Debian 7.4 (latest) 64-bit (amd64) into a VirtualBox virtual machine. Downloaded Eclipse Luna and tried to execute:

1) with default openjdk6;
2) installed openjdk7-jre to try with java 7;
3) installed kde-config-gtk-style package and used Settings -> Application appearance -> GTK to check if GTK2 style set to Raleigh (it was already and GTK3 style is set to default; there's no Raleigh choice available for GTK3).

All tries failed. Will attach crash reports.

Created attachment 241381
VirtualBox clean Debian 7 64-bit install; Java 6

Created attachment 241382
VirtualBox clean Debian 7 64-bit install; Java 7

Created attachment 241383
VirtualBox clean Debian 7 64-bit install; Java 7; Raleigh GTK2

(In reply to Mari Donkers from comment #12)
> Have install Debian 7.4 (latest) 64-bit (amd64) into a VirtualBox virtual
> machine. Downloaded Eclipse Luna and tried to execute:
>
> 1) with default openjdk6;
> 2) installed openjdk7-jre to try with java 7;
> 3) installed kde-config-gtk-style package and used Settings -> Application
> appearance -> GTK to check if GTK2 style set to Raleigh (it was already and
> GTK3 style is set to default; there's no Raleigh choice available for GTK3).
>
> All tries failed. Will attach crash reports.

BTW: Eclipse Kepler also works fine (in the virtual machine Debian 7 KDE 64-bit install).

So the problem is easily reproducible by doing a Debian 7.4 64-bit KDE install in a VirtualBox environment, install of Java packages, download of latest Eclipse Juno and attempt to start it.

From the logs we find that GTK2 and GTK3 have been loaded. This is not supposed to happen. Looks like due to some internal dependencies both gtk2 and gtk3 are getting loaded

Can you please let us know Whether this problem occurs with environment variable SWT_GTK3 set to 0?

For the comparision sake can you please attach the output of
lsof -p <pid>
for the JVM started by eclipse with SWT_GTK3 set to 0 and set to 1?

(In reply to Sravan Kumar Lakkimsetti from comment #18)
> From the logs we find that GTK2 and GTK3 have been loaded. This is not
> supposed to happen. Looks like due to some internal dependencies both gtk2
> and gtk3 are getting loaded
>
> Can you please let us know Whether this problem occurs with environment
> variable SWT_GTK3 set to 0?

THAT WORKS! Eclipse Luna starts normally when I first do the suggested:

   export SWT_GTK3=0

> For the comparision sake can you please attach the output of
> lsof -p <pid>
> for the JVM started by eclipse with SWT_GTK3 set to 0 and set to 1?

Will attach output for it set to 0 (not for 1 because it crashes and then there's
no jvm running)

Thanks for workaround and the support!

Created attachment 241915
Requested output of lsof -p <jvm-pid>

(In reply to Mari Donkers from comment #19)

> Will attach output for it set to 0 (not for 1 because it crashes and then
> there's no jvm running)
>

Will output for it set to 1 running under SolydK (i.e. a Debian Testing, tested distribution) where it does not crash.

Created attachment 241930
SWT_GTK3-set-to-1_SolyK.txt

Hi,

From the logs it seems that gtk3 libraries are loaded but wrong version platform interface(pi) library developed for eclipse is getting loaded.

There are two pi libraries libswt-pi and libswt-pi3. Whenever gtk3 is loaded libswt-pi3 should get loaded. but it looks like this library is not getting loaded.

One way to confirm is to check whether all the dependencies are satisfied using the ldd command

the pi libraries are present at <eclipse home>/configuration/org.eclipse.osgi/209/0/.cp/

send us the output of ldd libswt-pi3-gtk-<version>.so

This should reveal any missing dependencies

Also can you reproduce the problem with other JREs like Oracle JRE?

Thanks
Sravan

(In reply to Sravan Kumar Lakkimsetti from comment #23)
> Hi,
>
> From the logs it seems that gtk3 libraries are loaded but wrong version
> platform interface(pi) library developed for eclipse is getting loaded.
>
> There are two pi libraries libswt-pi and libswt-pi3. Whenever gtk3 is loaded
> libswt-pi3 should get loaded. but it looks like this library is not getting
> loaded.
>
> One way to confirm is to check whether all the dependencies are satisfied
> using the ldd command
>
> the pi libraries are present at <eclipse
> home>/configuration/org.eclipse.osgi/209/0/.cp/
>
> send us the output of ldd libswt-pi3-gtk-<version>.so
>
> This should reveal any missing dependencies

Will add attachment.

>
> Also can you reproduce the problem with other JREs like Oracle JRE?

Yes, see earlier posts. Most of the error logs I added are for Oracle JRE 8.

Created attachment 242107
LDD.txt

(In reply to Mari Donkers from comment #25)
> Created attachment 242107 [details]
> LDD.txt

Than you for the update. From the ldd out put we can clearly see that the glibc version is satisfied. The minimum version we require is glibc 2.14.

From the prior crash log we can see that glibc 2.13 is installed.

Can you please upgrade glibc to atleast 2.14 and verify?

In the meanwhile you can use setting SWT_GTK3=0 as workaround. This makes eclipse to use gtk2 instead of gtk3

Thanks
Sravan

(In reply to Sravan Kumar Lakkimsetti from comment #26)
> (In reply to Mari Donkers from comment #25)
> > Created attachment 242107 [details]
> > LDD.txt
>
> Than you for the update. From the ldd out put we can clearly see that the
> glibc version is satisfied. The minimum version we require is glibc 2.14.
>
> From the prior crash log we can see that glibc 2.13 is installed.
>
> Can you please upgrade glibc to atleast 2.14 and verify?

No can do... It's not delivered with Debian Wheezy and installing it from Debian testing or experimental sounds a bit fishy.

The page:

http://superuser.com/questions/537683/how-to-fix-lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-14-not-found/537694#537694

reads:

"Glibc is the library that everything depends on, so upgrading it can have far-reaching implications. Although there's probably nothing wrong with Debian's glibc 2.16 package, the fact that it's in the experimental repository means it hasn't received as much testing."

Eclipse Luna should be able to run on Debian 7.4 Wheezy stable out of the box because the stable distribution is used primarily by businesses (because it's stable and low maintenance).

(In reply to Mari Donkers from comment #27)
> (In reply to Sravan Kumar Lakkimsetti from comment #26)
> > (In reply to Mari Donkers from comment #25)
> > > Created attachment 242107 [details]
> > > LDD.txt
> >
> > Than you for the update. From the ldd out put we can clearly see that the
> > glibc version is satisfied. The minimum version we require is glibc 2.14.
> >
> > From the prior crash log we can see that glibc 2.13 is installed.
> >
> > Can you please upgrade glibc to atleast 2.14 and verify?
>
> No can do... It's not delivered with Debian Wheezy and installing it from
> Debian testing or experimental sounds a bit fishy.
>
> The page:
>
> http://superuser.com/questions/537683/how-to-fix-lib-x86-64-linux-gnu-libc-
> so-6-version-glibc-2-14-not-found/537694#537694
>
> reads:
>
> "Glibc is the library that everything depends on, so upgrading it can have
> far-reaching implications. Although there's probably nothing wrong with
> Debian's glibc 2.16 package, the fact that it's in the experimental
> repository means it hasn't received as much testing."
>
> Eclipse Luna should be able to run on Debian 7.4 Wheezy stable out of the
> box because the stable distribution is used primarily by businesses (because
> it's stable and low maintenance).

That said, your suggestion *does work* (Eclipse Luna starts fine) when I first install glibc 2.18, as instructed on the following page:

http://verahill.blogspot.nl/2014/03/562-pulling-in-glibc-214-from-testing.html

I'm seeing the same/similar crash.

Interestingly, for me it only happens in a runtime workbench!

I'm running Eclipse SDK I20130918-2000 on Kubuntu 12.04, works OK.
Inside the IDE I launch a runtime workbench with all platform bundles from the host. This runtime workbench crashes.

Due to various problems with GTK3 on this box I'm running with SWT_GTK3=0, but in the log I see libgtk-3.so.0.400.2 loaded. I even explicitly added SWT_GTK3=0 to the launch configuration's environment. Is this variable not evaluated in a runtime workbench??

glibc is 2.15 NPTL 2.15

(In reply to Stephan Herrmann from comment #29)
> I'm seeing the same/similar crash.
>
> Interestingly, for me it only happens in a runtime workbench!
>
> I'm running Eclipse SDK I20130918-2000 on Kubuntu 12.04, works OK.
> Inside the IDE I launch a runtime workbench with all platform bundles from
> the host. This runtime workbench crashes.
>
> Due to various problems with GTK3 on this box I'm running with SWT_GTK3=0,
> but in the log I see libgtk-3.so.0.400.2 loaded. I even explicitly added
> SWT_GTK3=0 to the launch configuration's environment. Is this variable not
> evaluated in a runtime workbench??
>
> glibc is 2.15 NPTL 2.15

All this works with I20140325-0830, so may not be relevant any more.

*** Bug 434559 has been marked as a duplicate of this bug. ***

Debian wheezy comes with glibc 2.13. For eclipse in gtk3 we need the minimum version to be 2.14.

To resolve the problem please upgrade the glibc version to 2.14.

We will be closing this as wont fix as upgrading glibc will resolve the problem

*** Bug 438174 has been marked as a duplicate of this bug. ***

Can you add a check for the glibc version?

I confirm that setting SWT_GTK3=0 solves this issue, not only on CDT but also on JEE.

I know Debian Wheezy is somewhat old for today's standards, but it works and I use it for work everyday. This issue can be fixed by adding a new check on the platform code, to detect if glibc version is 2.13 then set SWT_GTK3=0.

Thank you.

(In reply to Alejandro Santos from comment #34)
> Can you add a check for the glibc version?
>
> I confirm that setting SWT_GTK3=0 solves this issue, not only on CDT but
> also on JEE.
>
> I know Debian Wheezy is somewhat old for today's standards, but it works and
> I use it for work everyday. This issue can be fixed by adding a new check on
> the platform code, to detect if glibc version is 2.13 then set SWT_GTK3=0.
>
> Thank you.

Hi,

It will be difficult to make the change for debian wheezy as the glibc used there is quite old. I understand setting the flag everytime you need to start eclipse is slightly irritating. You can add the following lines to eclipse.ini to make it permanent

--launcher.GTK_version
2

This will force eclipse to use GTK 2 always

Thanks
Sravan

(In reply to Sravan Kumar Lakkimsetti from comment #35)
>
> It will be difficult to make the change for debian wheezy as the glibc used
> there is quite old.

What I mean is that, when Eclipse detects an old version of GLIBC, force the use of GTK2.

> I understand setting the flag everytime you need to
> start eclipse is slightly irritating. You can add the following lines to
> eclipse.ini to make it permanent
>
> --launcher.GTK_version
> 2
>

This change breaks my Eclipse launcher:

$ ./eclipse
Unrecognized option: --launcher.GTK_version
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

(In reply to Sravan Kumar Lakkimsetti from comment #35)
>
> --launcher.GTK_version
> 2
>
> This will force eclipse to use GTK 2 always
>

Never mind, I mixed the order on the eclipse.ini file (just noticed the vmargs arguments). It works now.

Thanks!

*** Bug 438342 has been marked as a duplicate of this bug. ***

*** Bug 438424 has been marked as a duplicate of this bug. ***

*** Bug 438588 has been marked as a duplicate of this bug. ***

*** Bug 438521 has been marked as a duplicate of this bug. ***

*** Bug 439436 has been marked as a duplicate of this bug. ***

Can someone provide a full eclipse.ini with the suggested patch.
I can run eclipse by running the export command prior to the launch.
But adding "--launcher.GTK_version 2" does not work for me on Debian Wheezy with Gnome.

(In reply to Dars Vaeda from comment #43)
> Can someone provide a full eclipse.ini with the suggested patch.
> I can run eclipse by running the export command prior to the launch.
> But adding "--launcher.GTK_version 2" does not work for me on Debian Wheezy
> with Gnome.

The option --launcher.GTK_version should be *before* --launcher.appendVmargs

Mine for CDT is:

$ cat eclipse.ini
-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.cpp.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=256m
-Xms40m
-Xmx1536m

Thx, I think the crucial part here was that the "2" is on a new line.

*** Bug 441931 has been marked as a duplicate of this bug. ***

*** Bug 442212 has been marked as a duplicate of this bug. ***

I am running KALI
PRETTY_NAME="Kali GNU/Linux 1.0"
NAME="Kali GNU/Linux"

I would like to add a resolve that by adding the line:

 --launcher.GTK_version
2

in the eclipse.ini form starting on the third line:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.GTK_version
2
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.standard.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
/usr/lib/jvm/jdk1.8.0_20/jre/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m

allows eclipse to function nominally. Also notice I running jdk1.8.0_20 as well.
Thank you for your efforts and research.

*** Bug 442741 has been marked as a duplicate of this bug. ***

The bug title mentions "KDE". Not relevant, I had the same problem with XFCE. Both workarounds solved the problem for me, i.e., either setting the environment variable SWT_GTK3=0 or else adding the two lines

    --launcher.GTK_version
    2

to eclipse.ini.

SWT_GTK3=0 must be used in fluxbox too,
i've a mixed enviroment with gtk2 and gtk3
whezzy and sid/ubuntu 14.04

cp to .swt does not work

I have the same issue with Eclipse Mars and Wheezy 64bit.
(Setting the env variable fixes it)

*** Bug 474849 has been marked as a duplicate of this bug. ***

I just ran into this after upgrading kubuntu to 15.10. Forcing GTK2 works. Using or not using the oxygen theme doesn't seem to matter.

Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200

Why is this bug marked as RESOLVED WONTFIX?

(In reply to Matt Parker from comment #54)
> I just ran into this after upgrading kubuntu to 15.10. Forcing GTK2 works.
> Using or not using the oxygen theme doesn't seem to matter.
>
> Version: Mars.1 Release (4.5.1)
> Build id: 20150924-1200
>
> Why is this bug marked as RESOLVED WONTFIX?

The root cause of problem reported here is the incompatible glib version. This problem would not appear in Kubuntu 15.10.

We found that the only version which is affected is Debian Wheezy and Jessie is around the corner so we decided not to fix this. The fix requires setting up of eclipse build system on Debian wheezy. Since the Debian wheezy is quite old and next version is around the corner we decided as not to proceed with the fix.

*** Bug 492318 has been marked as a duplicate of this bug. ***

Also occurs under recent OSes, sometimes at startup, sometimes after running a while

Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux
ldd (Debian GLIBC 2.24-11+deb9u4) 2.24

and

Linux p50 5.0.0-27-generic #28-Ubuntu

both running Gnome3

(In reply to Sravan Kumar Lakkimsetti from comment #26)
> In the meanwhile you can use setting SWT_GTK3=0 as workaround. This makes
> eclipse to use gtk2 instead of gtk3

This no longer works because GTK2 support was dropped from eclipse

Ubuntu glib-c version
ldd (Ubuntu GLIBC 2.29-0ubuntu2) 2.29

(In reply to Christoph Laeubrich from comment #57)
> Also occurs under recent OSes, sometimes at startup, sometimes after
> running a while
>
> Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux
> ldd (Debian GLIBC 2.24-11+deb9u4) 2.24
>
>
> and
>
> Linux p50 5.0.0-27-generic #28-Ubuntu

Which GTK3 versions are being used in these cases? Can you test with 4.13 (either GA or one of the RC versions) to confirm if the issue is still reproducible?

(In reply to Eric Williams from comment #59)
> (In reply to Christoph Laeubrich from comment #57)
> > Also occurs under recent OSes, sometimes at startup, sometimes after
> > running a while
> >
> > Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux
> > ldd (Debian GLIBC 2.24-11+deb9u4) 2.24
> >
> >
> > and
> >
> > Linux p50 5.0.0-27-generic #28-Ubuntu
>
> Which GTK3 versions are being used in these cases? Can you test with 4.13
> (either GA or one of the RC versions) to confirm if the issue is still
> reproducible?

Ping, any update here?

dpkg shows

libgtk-3-0:amd 3.22.11-1 amd64 GTK+ graphical user interface lib
libgtk-3-0:i38 3.22.11-1 i386 GTK+ graphical user interface lib
libgtk2.0-0:am 2.24.31-2 amd64 GTK+ graphical user interface lib
libgtk2.0-0:i3 2.24.31-2 i386 GTK+ graphical user interface lib

Has something changed here in 4.13 compared to 2019-06?

What I found out is that the crash seems to only happen for open-jdk builds but _seem_ to work fine on oracle-jdk.