thisis really odd because Eclipse randomly crashes, mostly if you use *any* close button like STRG+F and close the search window and some other places these are completly unexpected things if someone updates to Fedora 20 while there is no major change in the used software except libraries https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1205452 https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1205452/comments/7 http://forums.zend.com/viewtopic.php?f=59&t=114903 # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f710f967b48, pid=10954, tid=140124135044864 # # JRE version: OpenJDK Runtime Environment (7.0_45-b15) (build 1.7.0_45-mockbuild_2014_01_06_16_22-b00) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19b48] g_object_get_qdata+0x18 # # 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: # /tmp/jvm-10954/hs_error.log Compiled method (nm) 45799 890 n org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native) total in heap [0x00007f7125341750,0x00007f7125341ad0] = 896 relocation [0x00007f7125341870,0x00007f71253418d0] = 96 main code [0x00007f71253418e0,0x00007f7125341ad0] = 496 #
here another one https://bugs.kde.org/show_bug.cgi?id=324438 looks like there is even a patch https://bugs.kde.org/show_bug.cgi?id=324438#c36
oxygen-gtk2-1.4.2 with various fixes should be released soon.
oxygen-gtk2-1.4.2-1.fc20,oxygen-gtk3-1.3.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/oxygen-gtk2-1.4.2-1.fc20,oxygen-gtk3-1.3.2-1.fc20
as said while giving karma oxygen-gtk2-1.4.2-1.fc20 works *much* better but sadly not predictable clean enough, however, this update should be pushed because it makes things really better as before at night i tested all the cases where before in eclipse (Zend Studio 10.5.1 to be precise) and it looked perfect - where i still can repdrocude *unpredictable* a force close if by close the search dialog (CTRL+F), not always, not as i gave karma but that is still critical and may lead to lose changes / work
in the cases i can reproduce the "force close" it looks like the same issue as before ([libgobject-2.0.so.0+0x19b48) [harry@rh:~]$ ZendStudio # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ffa3e745b48, pid=23538, tid=140713467508480 # # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_17_13_38-b00) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19b48] g_object_get_qdata+0x18 # # 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: # /tmp/jvm-23538/hs_error.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 Machine in native code. # See problematic frame for where to report the bug.
See https://bugs.kde.org/show_bug.cgi?id=329814 > the crash also happens with qtcurve and might actually be upstream (gtk or swt)
i also made a bugreport for "glib2" and cross-linked this one because the named library file due crash in the terminal is from the glib2-package https://bugzilla.redhat.com/show_bug.cgi?id=1056070
oxygen-gtk2-1.4.2-1.fc20, oxygen-gtk3-1.3.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Unfortunately Eclipse is still crashing (when browsing variables during debug) using oxygen-gtk2-1.4.2-1.fc20 and oxygen-gtk3 1.3.3-3.fc20: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00000032328570c2, pid=10238, tid=140561260758784 # # JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-mockbuild_2014_01_31_16_21-b00) # Java VM: OpenJDK 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2570c2] gtk_tree_view_get_background_area+0xb2 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # 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 Machine in native code. # See problematic frame for where to report the bug. #
Still crashing for me on F20. I have oxygen-gtk2-1.4.2-1.fc20.x86_64 and oxygen-gtk3-1.3.3-3.fc20.x86_64.
Reverting to the latest oxygen-gtk* packages in the updates repo for Fedora 19 appears to cure the issue for me.
Sorry, I lied. Still crashing after downgrading oxygen-gtk*. I've now reverted back to the Fedora 19 versions of gtk2-* as well and still seeing crashes. Unfortunately, glib is a little more involved to downgrade as well but it's certainly looking like an upstream bug here.
It seems there is a patch for recent eclipse crash, see: https://bugs.kde.org/show_bug.cgi?id=339174 The patch applyes if you have in your log: void Oxygen::ComboBoxData::setButton(GtkWidget*): Assertion `!_button._widget' failed. Can we reopen this bug or do we need a new one?
May as well recycle this bug, re-opening.
In case no new release happens soon, upstream commits are: oxygen-gtk2: http://commits.kde.org/oxygen-gtk/1d25c917611546a944d3aee56fc792c4eab87d89 oxygen-gtk3: http://commits.kde.org/oxygen-gtk/68e4caa170f6103cd4a2b5e51a14190dc1fa6cbf
This bug ha been fixed in F21. Now I get in my log: Oxygen::WindowManager::wmButtonPress - warning: a button was already set for this combobox Eclipse doesn't crash anymore. $ rpm -qa oxygen-gtk* oxygen-gtk-1.2.0-6.fc21.noarch oxygen-gtk2-1.4.6-1.fc21.x86_64 oxygen-gtk3-1.4.1-1.fc21.x86_64
oxygen-gtk2-1.4.6-1.fc21, oxygen-gtk3-1.4.1-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2014-13526/oxygen-gtk2-1.4.6-1.fc21,oxygen-gtk3-1.4.1-1.fc21
Just tested with F20 and Eclipse Luna Service Release 1 (4.4.1). No more crashes, the same warning in log as above. $ rpm -q oxygen-gtk2 oxygen-gtk2-1.4.6-1.fc20.x86_64
oxygen-gtk2-1.4.6-1.fc21, oxygen-gtk3-1.4.1-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
But it still crash in my Fedora21, here is the info: [will@will DeviceQuery]$ /usr/local/cuda-6.5/bin/nsight Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 CompilerOracle: exclude java/lang/reflect/Array.newInstance # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fcfd8db9ebd, pid=8055, tid=140531122136832 # # JRE version: Java(TM) SE Runtime Environment (8.0_20-b26) (build 1.8.0_20-b26) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.20-b23 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x32ebd] g_type_check_instance_is_fundamentally_a+0xd # I am using Fedora21 with KDE. the xoygen-gtk version: rpm -qa oxygen-gtk* oxygen-gtk3-1.4.1-3.fc21.x86_64 oxygen-gtk-1.2.0-6.fc21.noarch oxygen-gtk2-1.4.6-1.fc21.x86_64