GNOME Bugzilla – Bug 736323
SIGSEGV on disposing combo with appears-as-list=1
Last modified: 2018-04-15 00:02:34 UTC
We have a java RCP application (basing on Eclipse 3.7.1 RCP) that we observe reproducable crashes since having upgraded to openSuSE 13.1 with KDE desktop, gtk2 2.24.22-2.1. It happens always when closing a view. The java error file shows, that this is related to de-registering a combobox within a widget contained (see hs_err_pid8531.log that I will attach). It happens only with using a GTK2 theme having enabled the GtkComboBox::appears-as-list. AFAIK this is the case only for the oxygen-gtk2 theme at the moment. But it is no matter of this specigic theme, I can force this error also with configuring the Raleigh theme to have this option enabled. See also https://bugs.kde.org/show_bug.cgi?id=329814. It gehaves the same was (crash with appears-as-list=1, stable with 0) for an older version of our application basing on eclipse RCP 3.5.0. So this should not be responsible for this crash, too.
This seems a rather popular problem with most people actually blaming the oxygen-gtk2 theme to be responsible. I found several similar bug requests with googling for e.g. "libgobject-2.0.so g_object_get_qdata" or "org.eclipse.swt.internal.gtk.OS._g_object_get_qdata" as such being contained within the java error report files. IMHO the eclipse IDE seems affected, too, with running in the a.m. environment. I would have voted even for critical priority - but with the workaround to disable the appears-as-list I voted for major "only". I'm on the way to check additionally, if the same error applies for an older distro.
I've seen that bug crashing all eclipse related application I'm using like apachedirectory studio, ZendStudio Xmind etc ... probably the most annoying long term thing viewed :-) Thanks to have found the what is the root cause.
This looks like https://bugs.eclipse.org/bugs/show_bug.cgi?id=372560 so a newer SWT version should fix it, e.g. the one coming with Eclipse 4.3. I had the same problem and fixed it by applying the patch myself to SWT that comes with Eclipse 3.8.2, so this could be an option if you have to stay on Eclipse 3.x.
Can anyone confirm if this still occurs? i.e. did the above fix it? If it still occurs, maybe the cause is similar to https://bugzilla.gnome.org/show_bug.cgi?id=703511
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new