GNOME Bugzilla – Bug 755328
[SWT] gtk 3.17.9 makes eclipse crash
Last modified: 2015-09-23 17:43:48 UTC
This is an upstream bug corresponding to: https://bugzilla.redhat.com/show_bug.cgi?id=1264388 Latest gtk 3.17.9 makes eclipse crash for me. If I launch eclipse from a terminal I get a crash in libgdk-3.so: $ rm -rf remove_me_workspace && eclipse -data remove_me_workspace $ rpm -qa | grep gtk ibus-gtk2-1.5.11-1.fc23.x86_64 caribou-gtk2-module-0.4.18.1-2.fc23.x86_64 authconfig-gtk-6.2.10-10.fc23.x86_64 pygtk2-2.24.0-12.fc23.x86_64 webkitgtk3-2.4.9-2.fc23.x86_64 clutter-gtk-1.6.4-1.fc23.x86_64 gtkmm24-2.24.4-7.fc23.x86_64 gtk3-3.17.9-1.fc23.x86_64 gtk-vnc-0.5.4-2.fc23.x86_64 libcanberra-gtk3-0.30-10.fc23.x86_64 usermode-gtk-1.111-7.fc23.x86_64 pygtk2-libglade-2.24.0-12.fc23.x86_64 gtk2-devel-2.24.28-2.fc23.x86_64 gtk2-engines-2.20.2-10.fc23.x86_64 PackageKit-gtk3-module-1.0.9-1.fc23.x86_64 adwaita-gtk2-theme-3.16.2-2.fc23.x86_64 libnm-gtk-1.0.6-3.fc23.x86_64 gtk-update-icon-cache-3.17.9-1.fc23.x86_64 gtksourceview3-3.17.7-1.fc23.x86_64 pywebkitgtk-1.1.8-10.fc23.x86_64 gtkhtml3-4.9.92-1.fc23.x86_64 xdg-user-dirs-gtk-0.10-8.fc23.x86_64 colord-gtk-0.1.26-2.fc23.x86_64 libcanberra-gtk2-0.30-10.fc23.x86_64 libreport-gtk-2.6.2-5.fc23.x86_64 spice-gtk3-0.29-4.fc23.x86_64 python-slip-gtk-0.6.4-1.fc23.noarch gtk-vnc-python-0.5.4-2.fc23.x86_64 gtkspell-2.0.16-10.fc23.x86_64 avahi-ui-gtk3-0.6.31-40.fc23.x86_64 gtk2-immodule-xim-2.24.28-2.fc23.x86_64 libchamplain-gtk-0.12.10-2.fc23.x86_64 gtk-vnc2-0.5.4-2.fc23.x86_64 gtkmm30-3.17.4-1.fc23.x86_64 spice-gtk-python-0.29-4.fc23.x86_64 webkitgtk-2.4.9-2.fc23.x86_64 pinentry-gtk-0.9.6-1.fc23.x86_64 gtkspell3-3.0.7-2.fc23.x86_64 webkitgtk4-2.9.92-1.fc23.x86_64 transmission-gtk-2.84-8.fc23.x86_64 gtk2-2.24.28-2.fc23.x86_64 gtk3-immodule-xim-3.17.9-1.fc23.x86_64 ibus-gtk3-1.5.11-1.fc23.x86_64 caribou-gtk3-module-0.4.18.1-2.fc23.x86_64 spice-gtk-0.29-4.fc23.x86_64 $ rpm -qa | grep eclipse eclipse-e4-importer-0.1.0-0.3.git5ac5197.fc23.noarch eclipse-swt-4.5.0-14.fc23.x86_64 eclipse-webtools-servertools-3.7.0-1.fc23.noarch eclipse-jgit-4.0.1-4.fc23.noarch eclipse-remote-2.0.0-1.fc23.noarch eclipse-rse-3.7.0-2.fc23.noarch eclipse-p2-discovery-4.5.0-14.fc23.noarch eclipse-gef-3.10.0-1.fc23.noarch eclipse-linuxtools-4.0.0-6.fc23.noarch eclipse-dtp-1.12.0-5.fc23.noarch eclipse-equinox-osgi-4.5.0-14.fc23.x86_64 eclipse-m2e-workspace-0.2.0-2.fc23.noarch eclipse-webtools-common-core-3.7.0-1.fc23.noarch eclipse-webtools-sourceediting-3.7.0-1.fc23.noarch eclipse-ptp-9.0.0-1.fc23.x86_64 eclipse-filesystem-1.0-5.fc23.x86_64 eclipse-cdt-8.7.0-8.fc23.x86_64 eclipse-webtools-servertools-core-3.7.0-1.fc23.noarch eclipse-linuxtools-libhover-4.0.0-6.fc23.noarch eclipse-emf-runtime-2.11.0-3.fc23.noarch eclipse-xsd-2.10.1-4.fc23.noarch eclipse-emf-core-2.11.0-3.fc23.x86_64 eclipse-mylyn-docs-wikitext-3.16.0-2.fc23.noarch eclipse-m2e-core-1.6.1-1.fc23.noarch eclipse-pde-4.5.0-14.fc23.x86_64 eclipse-cdt-parsers-8.7.0-8.fc23.x86_64 devassistant-dap-eclipse-0.10.0dev-9.fc23.noarch eclipse-jdt-4.5.0-14.fc23.x86_64 eclipse-egit-4.0.1-4.fc23.noarch eclipse-fedorapackager-0.5.0-5.fc23.noarch eclipse-mylyn-3.16.0-2.fc23.noarch eclipse-changelog-4.0.0-6.fc23.noarch eclipse-debuginfo-4.5.0-14.fc23.x86_64 eclipse-platform-4.5.0-14.fc23.x86_64 eclipse-ecf-core-3.10.1-1.fc23.x86_64 maven-eclipse-plugin-2.9-14.fc23.noarch eclipse-rpm-editor-4.0.0-6.fc23.noarch eclipse-webtools-common-3.7.0-1.fc23.noarch eclipse-tm-terminal-4.0.0-2.fc23.noarch
Created attachment 311735 [details] hotspot error file
Created attachment 311736 [details] another hotspot error report file
Downgrading to packages gtk3-3.17.8-2.fc23.x86_64 and gtk3-immodule-xim-3.17.8-2.fc23.x86_64 fixes the problem for me.
I tried to reproduce it and it reproducibly crashes here with gtk+ master. Looks like a fallout from the object reffing optimization in https://git.gnome.org/browse/gtk+/commit/?id=eafedfbaf8e080a1e444f46cde082fb2734552f9 Here's the backtrace:
+ Trace 235479
Reverting https://git.gnome.org/browse/gtk+/commit/?id=eafedfbaf8e080a1e444f46cde082fb2734552f9 fixes it. Looking further.
this was fixed in 3.18.0