SIGSEGV when running eclipse 3.8

[Hceylan]

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ffbe4ab4e8c, pid=9667, tid=140720205301504
#
# JRE version: 7.0_07-b30
# Java VM: OpenJDK 64-Bit Server VM (23.2-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgobject-2.0.so.0+0x32e8c] g_type_check_instance_cast+0x1c
#
# 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:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[Anders Norgaard (anders-norgaard)]

Happens for me both on JDK7 and JDK6

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f28a4de1e8c, pid=23525, tid=139812748027648
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.11.4
# Distribution: Ubuntu quantal (development branch), package 6b24-1.11.4-3ubuntu1
# Problematic frame:
# C [libgobject-2.0.so.0+0x32e8c] g_type_check_instance_cast+0x1c
#
# An error report file with more information is saved as:
# /home/anders/hs_err_pid23525.log
[thread 139812147222272 also had an error]
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Vorburger (mike-vorburger)]

Happens occasionally (every couple of days) for me too, but no clear steps to reproduce (contrary to Bug 1056238 which I can repro).

[Hceylan (hceylan)]

Good that you can reproduce.

I too have it on randomly. However, for a fresh workspace with Welcome Screen on and full, closing the Welcome Screen by clicking the X crashes every time.

[Christopher Nelson (nadiasvertex)]

Happens to me everytime I start eclipse now. Eclipse ran fine for quite some time. Then in the middle of a session it aborted, and now I get this:

cnelson@tdvm:~$ /store/local/eclipse/eclipse -clean
Xlib: extension "RANDR" missing on display ":0".
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f09ef8cb5a0, pid=2990, tid=139681593820928
#
# JRE version: 7.0_07-b30
# Java VM: OpenJDK 64-Bit Server VM (23.2-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-1.0.so.0+0x14245a0] void WTF::freeOwnedGPtr<_GdkEvent>(_GdkEvent*)+0x15df0
#
# 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/cnelson/hs_err_pid2990.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[Derek Chafin (infomaniac50)]

Seems to always happen when Eclipse opens a web browser. I can't even use Eclipse because of this. It opens and then it crashes because the CFEclipse plugin tries to show it's welcome page.

[Cyril Jaquier (cyril-jaquier)]

Any workaround for this issue? I guess installing the Oracle JVM for now is the only solution...

[Robin Sheat (eythian)]

A workaround I found:

export GDK_NATIVE_WINDOWS=true

[Robin Sheat (eythian)]

Oh, I take that back. It was something else that apparently made it work. I ended up creating a new workspace (with that envvar set, in case it helps) and after a bit of messing around with the old and the new workspace, it seems to have started working.

[Konstantin (tkachenkok)]

I've got the same error on starting eclipse from the console.

But I had slightly different message:
# JRE version: 7.0_13-b20
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgobject-2.0.so.0+0x192c0] g_object_get_qdata+0x20

Starting eclipse from the desktop icon fails (with crash directly after workspace selection.)

Strange thing - after executing command mensioned in the error message ("ulimit -c unlimited"), starting eclipse succeeded. That was first eclipse execution after installation and I tried to select a non-default workspace with one unpacked python-project in it (located on ntfs-partition).
So I could install pydev extension to eclipse and wanted to test it one more time.

Starting from desktop still was not possible, starting from the same terminal for default workspace (to be initialized) succeeded one more time. Starting eclipse from another terminal failed.

General repitition:
- exit from terminal
- starting via desktop launcher failed after non-default workspace location
- start terminal
- starting eclipse from terminal crashes the same way
- execute "ulimit -c unlimited"
- starting eclipse from terminal !!!CRASHES!!! :(:(:(

It looks like really annoying hard bug...

[Bruno Girin (brunogirin)]

I can confirm that I had the same crash when starting Eclipse on a brand new workspace and trying to dismiss the welcome screen. It didn't happen on subsequent startups.

[Johannes (johannes-claesson)]

Applies to Eclipse 3.8 as well as Juno. Applies to openjdk-7 and openjdk-6 as well as oracle-java7 and oracle-java8.

[3vi1 (launchpad-net-eternaldusk)]

I have this crash everytime I start eclipse on a new 64-bit saucy install. It doesn't matter whether I point the workspace directory to a new path or directory that already exists.

Has anyone found a workaround that will allow Eclipse to start, short of resorting to the old Oracle version?

[kimus (kimus)]

Same problem in Ubuntu 13.10 with several Java based applications (i.e: SmartGit)

[Ke Xu (kxu1985)]

A workaround I found is to manually type the workspace directory, instead of clicking "browser..." and choosing one automatically. I can confirm Eclipse 3.8 work after that. I am using Mint 15.

[Dima Ryazanov (dima-gmail)]

I get a crash pretty much every time when I try to install a plugin:
- Help->Install New Software...
- Add... or select an existing URL
- Click Next
- Click Finish

The "Finish" button stays in the pressed state for a few seconds, then Eclipse crashes.

[Dima Ryazanov (dima-gmail)]

Actually, even easier:
- Click Help->Install New Software...
- Click Cancel

[Si P. (si-lp)]

I'm getting repeated crashes on a different frame. I've tried to find a way of repeating it but can't.

It's on a clean 3 day old Saucy install.

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fcb99e2392a, pid=5657, tid=140512902682368
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgtk-x11-2.0.so.0+0x24492a] gtk_widget_queue_draw+0x1a
#
# Core dump written. Default location: /home/si/core or core.5657
#
# An error report file with more information is saved as:
# /home/si/hs_err_pid5657.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[MartinSt (martinstingl)]

Here is the information from the crash at my machine:
http://pastebin.com/WPzMHU7k