Community
Participate
Working Groups
Created attachment 272695 [details] Error report file Steps to reproduce: 1. Start Eclipse on an empty workspace and open the "Problems" view. 2. Click with the left mouse button on a column in the view and hold the button. 3. Now move the cursor horizontal so that the columns get reorderd. 4. While moving the columns around press escape. Expected result: The columns go back to their original place without being reorderd. Actual result: The JVM crashes. Console output: 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. org.eclipse.m2e.logback.configuration: Logback config file: /home/toh/eclipse-empty-workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.8.2.20171007-0217.xml SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [bundleresource://999.fwk762722278:1/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundleresource://999.fwk762722278:2/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] org.eclipse.m2e.logback.configuration: Initializing logback # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f2fb5759de9, pid=6455, tid=0x00007f305ac10700 # # JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.162-b12 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-3.so.0+0x2b1de9] # # Core dump written. Default location: /home/toh/eclipse-oxygen-2/core or core.6455 # # An error report file with more information is saved as: # /home/XXXX/eclipse-oxygen-2/hs_err_pid6455.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # Error report file is attached. I also have a core dump file but it is 118 MB big. Where can I upload it? I did intentionally not report to Oracle first as their bug form says "If the crash occurred while running a product developed by a company other than Oracle, please report this issue to the vendor of that product." The bug is reproducible every time using the steps above. System under test: Kubuntu 14.04.5 LTS Oxygen.2 Release (4.7.2) Build id: 20171218-0600 JDK jdk1.8.0_162 from Oracle
Which GTK+ theme are you using, and which version of GTK3?
Theme for GTK3 is clearlooks-phenix-5 but I'm running KDE 4.13.3 Below are the information for two gtk3 packages. Do you need information for other packages? #apt-cache show libgtk-3-0:amd64 Package: libgtk-3-0 Architecture: amd64 Version: 3.10.8-0ubuntu1.6 Multi-Arch: same Priority: optional Section: libs Source: gtk+3.0 Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 6562 Provides: gtk3-binver-3.0.0 Pre-Depends: multiarch-support Depends: libgtk-3-common (>= 3.10.8), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 2.7.5), libc6 (>= 2.14), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.13.0~20140204), libcolord1 (>= 0.1.10), libcups2 (>= 1.6.2), libfontconfig1 (>= 2.9.0), libgdk-pixbuf2.0-0 (>= 2.27.1), libglib2.0-0 (>= 2.39.4), libpango-1.0-0 (>= 1.32.4), libpangocairo-1.0-0 (>= 1.32.4), libpangoft2-1.0-0 (>= 1.32.4), libwayland-client0 (>= 1.3.92), libwayland-cursor0 (>= 1.2.0), libx11-6 (>= 2:1.4.99.1), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxinerama1, libxkbcommon0 (>= 0.2.0-0ubuntu3~), libxrandr2 (>= 2:1.2.99.3), shared-mime-info Recommends: hicolor-icon-theme, libgtk-3-bin Suggests: librsvg2-common, gvfs Breaks: gnome-themes-standard (<< 3.6), gtk3-engines-unico (<< 1.0.2-0ubuntu2), libvte-2.90-9 (<< 1:0.32), libwebkitgtk-3.0-0 (<< 1.8.0), murrine-themes (<= 0.98.2) Filename: pool/main/g/gtk+3.0/libgtk-3-0_3.10.8-0ubuntu1.6_amd64.deb Size: 1960312 MD5sum: 689f31ab08568e18f46a81ec557ad735 SHA1: 05bb104e62379d03abada6a5eadb39ef0e76a685 SHA256: 210daf4eac10b9067beaee1976e3e2ac613ef1f9d2ecc399a8fd98e0918b7ebc #apt-cache show libgtk-3-bin Package: libgtk-3-bin Architecture: amd64 Version: 3.10.8-0ubuntu1.6 Multi-Arch: foreign Priority: optional Section: misc Source: gtk+3.0 Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 157 Depends: libc6 (>= 2.2.5), libglib2.0-0 (>= 2.37.5), libgtk-3-0 (>= 3.10.8-0ubuntu1.6), libgtk-3-common (>= 3.10.8) Filename: pool/main/g/gtk+3.0/libgtk-3-bin_3.10.8-0ubuntu1.6_amd64.deb Size: 18188 MD5sum: fc4794ab07e15734a28722d9c12ea0c8 SHA1: 6a811299d2dcc456117f268ed91b912a90c14f11 SHA256: a90b7018cbfcaaf4589a9079272e3e451f9d0193aa08c35c16971163ea654ab3 Homepage: http://www.gtk.org/ Description-de: Programme für die GTK+-Bibliothek für grafische Benutzeroberflächen GTK+ ist eine plattformübergreifende Werkzeugsammlung zum Erstellen von grafischen Benutzeroberflächen. Da sie einen vollständigen Satz an Widgets bietet, ist GTK+ geeignet für Projekte von kleinen Einmal-Programmen bis hin zu vollständigen Anwendungs-Suiten. . Dieses Paket enthält die Hilfsprogramme, die von den Bibliotheken und anderen Paketen genutzt werden. Description-md5: 35573b29e3a6877ccd55de7c6873d715 Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, kubuntu-active-live, kubuntu-active-desktop, kubuntu-active-full, kubuntu-active-live, edubuntu-desktop, edubuntu-usb, xubuntu-desktop, mythbuntu-frontend, mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-slave, mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-core, ubuntustudio-desktop, ubuntu-gnome-desktop Phased-Update-Percentage: 0 Supported: 5y Package: libgtk-3-bin Architecture: amd64 Version: 3.10.8-0ubuntu1.4 Multi-Arch: foreign Priority: optional Section: misc Source: gtk+3.0 Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 157 Depends: libc6 (>= 2.2.5), libglib2.0-0 (>= 2.37.5), libgtk-3-0 (>= 3.10.8-0ubuntu1.4), libgtk-3-common (>= 3.10.8) Filename: pool/main/g/gtk+3.0/libgtk-3-bin_3.10.8-0ubuntu1.4_amd64.deb Size: 18176 MD5sum: c0bdf6dd9ba8bd1e3f1beef2e9cecd30 SHA1: 7c84594ef3edda4bdb6497e06c86f04428b6f747 SHA256: c41dd92fce39a2afd66880b34c605a80e72b0f55d0dfe2caae3fe45e5cd8599f
I can't reproduce on RHEL 7.2 / GTK 3.14 and RHEL 7.4 / GTK 3.22, both using default Adwaita and custom Clearlooks-Phenix themes. > 2. Click with the left mouse button on a column in the view and hold the button. Any column, or a specific one? 3. Now move the cursor horizontal so that the columns get reorderd. Any direction, or left/right only? However during my tests on GTK 3.22 (not on 3.14) I've seen those errors printed to the console: (Eclipse:32210): Gtk-WARNING **: Allocating size to GtkButton 0x7ffff28dd180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:32210): Gtk-WARNING **: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node button, owner GtkButton) (Eclipse:32210): Gtk-WARNING **: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node button, owner GtkButton)
I see that this is ubuntu - are overlay scrollbars enabled? Can you disable them and try again?
(In reply to Andrey Loskutov from comment #3) > [...] > > 2. Click with the left mouse button on a column in the view and hold the button. > > Any column, or a specific one? Any column. > > 3. Now move the cursor horizontal so that the columns get reorderd. > > Any direction, or left/right only? Any direction. > [...]
(In reply to Andrey Loskutov from comment #4) > I see that this is ubuntu - are overlay scrollbars enabled? Can you disable > them and try again? How can I check this? The package overlay-scrollbar is NOT installed.
Gtk 3.10.8, would you please try with different Gtk theme (e.g. Adwaita) and let us know whether the crash still happens.
(In reply to Alexander Kurtakov from comment #7) > Gtk 3.10.8, would you please try with different Gtk theme (e.g. Adwaita) and > let us know whether the crash still happens. I tried with oxygen-gtk and the problem still occurs. Adwaita is not installed, but I could get if it is necessary.
(In reply to Tobias Hirning from comment #8) > (In reply to Alexander Kurtakov from comment #7) > > Gtk 3.10.8, would you please try with different Gtk theme (e.g. Adwaita) and > > let us know whether the crash still happens. > I tried with oxygen-gtk and the problem still occurs. Adwaita is not > installed, but I could get if it is necessary. Oxygen is known to cause crashers :-/ Yes, could you try with Adwaita/Gnome3 if possible? Do you have access to gtk3.22? There's quite a considerable difference between gtk3.10 and gtk3.22.
(In reply to Leo Ufimtsev from comment #9) > (In reply to Tobias Hirning from comment #8) > > [...] > Oxygen is known to cause crashers :-/ > > Yes, could you try with Adwaita/Gnome3 if possible? > Do you have access to gtk3.22? There's quite a considerable difference > between gtk3.10 and gtk3.22. I could not find the Adwaita theme but tried with the Emacs theme. The problem still occurs with it. I also tried with Kubuntu 17.10 in a virtual machine with the theme Breeze and GTK 3.22.25-ubuntu0.1: The JVM does _not_ crash. But I see warnings when moving the columns: (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkScrolledWindow 0x7f2c5c9e0490 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkButton) (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkButton) (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkButton) (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkButton)
(In reply to Tobias Hirning from comment #10) > (In reply to Leo Ufimtsev from comment #9) > > (In reply to Tobias Hirning from comment #8) > > > [...] > > Oxygen is known to cause crashers :-/ > > > > Yes, could you try with Adwaita/Gnome3 if possible? > > Do you have access to gtk3.22? There's quite a considerable difference > > between gtk3.10 and gtk3.22. > I could not find the Adwaita theme but tried with the Emacs theme. The > problem still occurs with it. > > I also tried with Kubuntu 17.10 in a virtual machine with the theme Breeze > and GTK 3.22.25-ubuntu0.1: The JVM does _not_ crash. > > But I see warnings when moving the columns: > (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkScrolledWindow > 0x7f2c5c9e0490 without calling gtk_widget_get_preferred_width/height(). How > does the code know the size to allocate? > > (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04340 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, > extents 6x6) while allocating gadget (node button, owner GtkButton) > > (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04500 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, > extents 6x6) while allocating gadget (node button, owner GtkButton) > > (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04500 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, > extents 6x6) while allocating gadget (node button, owner GtkButton) > > (Eclipse:2912): Gtk-WARNING **: Allocating size to GtkButton 0x7f2c5ed04340 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > (Eclipse:2912): Gtk-WARNING **: Negative content width -11 (allocation 1, > extents 6x6) while allocating gadget (node button, owner GtkButton) Feel free to ignore allocation warnings. It's caused by other stuff, we've been meaning to fix it for a while: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486068 I've tried with Clearlooks-phenix 7 on my Feodra 27 with Gtk3.22. I've moved the columns all over the place, but had no crashes. I've also tried with Clearlooks-phenix 7 with Gtk3.14, no crashes still. I think it's an issue that's probably been fixed in either the themes or in a gtk version. (emacs theme might be buggy also). I suggest try to use new Gtk (3.22) and new/modern theme. Also try latest eclipse as they contain lots of crash fixes: http://download.eclipse.org/eclipse/downloads/ Let me know if I can help further. Thanks.
(In reply to Leo Ufimtsev from comment #11) > [...] > > [...] > I've tried with Clearlooks-phenix 7 on my Feodra 27 with Gtk3.22. I've moved > the columns all over the place, but had no crashes. > I've also tried with Clearlooks-phenix 7 with Gtk3.14, no crashes still. Did you also press "Escape" while moving? > I think it's an issue that's probably been fixed in either the themes or in > a gtk version. (emacs theme might be buggy also). > > I suggest try to use new Gtk (3.22) and new/modern theme. Also try latest > eclipse as they contain lots of crash fixes: > http://download.eclipse.org/eclipse/downloads/ I tried with the 4.8 integration build I20180220 and the problem was still present. eclipse-SDK-I20180218-2000-linux-gtk-x86_64.tar.gz
On crash a *.core file should be generated from it one can generate backtrace using gdb, can you please attach it?
(In reply to Alexander Kurtakov from comment #13) > On crash a *.core file should be generated from it one can generate > backtrace using gdb, can you please attach it? Yes, I have the core file: > Error report file is attached. I also have a core dump file but it is 118 MB > big. Where can I upload it?
(In reply to Tobias Hirning from comment #14) > (In reply to Alexander Kurtakov from comment #13) > > On crash a *.core file should be generated from it one can generate > > backtrace using gdb, can you please attach it? > > Yes, I have the core file: > > Error report file is attached. I also have a core dump file but it is 118 MB > > big. Where can I upload it? Well, we need just the backtrace from it. Steps should be: * gdb /path/to/eclipse corefile * `bt` in the gdb console
(In reply to Tobias Hirning from comment #12) > Did you also press "Escape" while moving? I actually didn't press escape, good point. With that said, I just tried pressing escape and the crash still did not occur with clear-phonix-7. <Awaiting gdb stack trace>
#gdb /usr/bin/java core Reading symbols from /usr/bin/java...(no debugging symbols found)...done. [New LWP 13617] [New LWP 13624] [New LWP 13622] [New LWP 13618] [New LWP 13619] [New LWP 13623] [New LWP 13631] [New LWP 13620] [New LWP 13632] [New LWP 13630] [New LWP 13629] [New LWP 13625] [New LWP 13621] [New LWP 13640] [New LWP 13637] [New LWP 13655] [New LWP 13635] [New LWP 13641] [New LWP 13639] [New LWP 13654] [New LWP 13627] [New LWP 13648] [New LWP 13672] [New LWP 13636] [New LWP 13653] [New LWP 13642] [New LWP 13628] [New LWP 13667] [New LWP 13690] [New LWP 13698] [New LWP 13656] [New LWP 13699] [New LWP 13638] [New LWP 13678] [New LWP 13650] [New LWP 13716] [New LWP 13692] [New LWP 13712] [New LWP 13704] [New LWP 13643] [New LWP 13685] [New LWP 13652] [New LWP 13616] [New LWP 13644] [New LWP 13626] [New LWP 13634] [New LWP 13669] [New LWP 13688] [New LWP 13676] [New LWP 13633] [New LWP 13679] [New LWP 13715] [New LWP 13677] [New LWP 13680] [New LWP 13706] [New LWP 13751] [New LWP 13722] [New LWP 13710] [New LWP 13713] [New LWP 13709] [New LWP 13695] [New LWP 13645] [New LWP 13711] [New LWP 13694] [New LWP 13707] [New LWP 13708] [New LWP 13693] [New LWP 13705] [New LWP 13646] [New LWP 13703] [New LWP 13647] [New LWP 13697] [New LWP 13657] [New LWP 13681] [New LWP 13649] [New LWP 13696] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/java -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user'. Program terminated with signal SIGABRT, Aborted. #0 0x00007ffff740fc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x00007ffff740fc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007ffff7413028 in __GI_abort () at abort.c:89 #2 0x00007ffff6d07f35 in os::abort(bool) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #3 0x00007ffff6eabf33 in VMError::report_and_die() () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #4 0x00007ffff6eac42e in crash_handler(int, siginfo*, void*) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #5 <signal handler called> #6 0x00007ffff697bab5 in G1CollectedHeap::is_in(void const*) const () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #7 0x00007ffff6cfe7d1 in os::print_location(outputStream*, long, bool) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #8 0x00007ffff6d0db7b in os::print_register_info(outputStream*, void*) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #9 0x00007ffff6eaa5a3 in VMError::report(outputStream*) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #10 0x00007ffff6eabb2a in VMError::report_and_die() () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #11 0x00007ffff6d0e22f in JVM_handle_linux_signal () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #12 0x00007ffff6d04253 in signalHandler(int, siginfo*, void*) () from /home/XXXX/YYYY/jdk1.8.0_162/jre/lib/amd64/server/libjvm.so #13 <signal handler called> #14 0x00007fff529d1de9 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #15 0x00007fff529d85bf in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #16 0x00007fff528c1c4c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x00007fff55e65332 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #18 0x00007fff55e76afb in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x00007fff55e7e6f9 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x00007fff55e7ece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x00007fff529ea974 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #22 0x00007fff52a076fb in gtk_window_propagate_key_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x00007fff52a0a94b in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #24 0x00007fff528c1c4c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #25 0x00007fff55e653b8 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x00007fff55e76afb in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x00007fff55e7e6f9 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #28 0x00007fff55e7ece2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x00007fff529ea974 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x00007fff528c01af in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #31 0x00007fff528c191a in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #32 0x00007fff4945101a in Java_org_eclipse_swt_internal_gtk_OS__1gtk_1main_1do_1event () from /home/XXXX/eclipse-oxygen-2/configuration/org.eclipse.osgi/786/0/.cp/libswt-pi3-gtk-4763.so #33 0x00007fffe189b039 in ?? () #34 0x00007ffff7fc9720 in ?? () #35 0x00007fffe1878304 in ?? () #36 0x0000000000000000 in ?? () Looks like I do need debug symbols java?
It looks like the stacktrace points too deep into gtk/java for this to be SWT specific and without us being to reproduce it with recent gtk/swt builds, we can't investigate it further. I don't think debug symbols would help much in this case either. Based on the fact that this issue only occurs in (correct me if I'm wrong?) Gtk3.10 (old version of gtk, newest is gtk3.22), and a custom theme, it seems to me that the bug is probably somewhere in either Gtk3.10 or in the custom theme. In which case we can't fix such a problem at the SWT level unfortunately. Suggestions: - 1) Update to latest gtk, 3.22 - 2) If it's an option, experiment with Gnome3 & adwaita. It might work more stable than KDE/Clear-Phonix. - (not reccomended) but if you can't update to newer gtk and can't use gnome3/adwaita, consider using gtk until you can update your system to newer gtk3. export SWT_GTK3=0. But you should keep in mind that gtk2 support is being deprecated. See: 530841 – (gtk2StatusInfo) [GTK2] Gtk 2.x currently not under development: focus on Gtk 3.x show stoppers. https://bugs.eclipse.org/bugs/show_bug.cgi?id=530841 To continue the investigation, you need to see if there is a way to reproduce the issue with Gtk3.22 (ish) and a more stable theme like Adwaita, such that we can test/investigate. Otherwise I think it might make sense to close as worksforme as crash seems to originate outside of swt. wdyt? Please let me know if we can help further.
As I can not reproduce the problem with GTK 3.22.25-ubuntu0.1 I also would agree in closing this bug.
(In reply to Tobias Hirning from comment #19) > As I can not reproduce the problem with GTK 3.22.25-ubuntu0.1 I also would > agree in closing this bug. Thank you for the crash report. Please feel free to submit them if you still run into them in newer versions. We appreciate your time.
