I'm also seeing instability with SIGSEVs in the native code when running eclipse. I tried the SWT_GTK3=0 workaround, but got the following crash:
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f5f9d789d6c, pid=7849, tid=140048942749440 # # JRE version: Java(TM) SE Runtime Environment (7.0_60-b19) (build 1.7.0_60-b19) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.60-b09 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x31d6c] g_type_check_instance_is_a+0x3c # # 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/rmuil/hs_err_pid7849.log Compiled method (nm) 87459 1185 n org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native) total in heap [0x00007f5fa517f290,0x00007f5fa517f610] = 896 relocation [0x00007f5fa517f3b0,0x00007f5fa517f410] = 96 main code [0x00007f5fa517f420,0x00007f5fa517f610] = 496 # # 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. # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
