JVM crash for Eclipse kepler 4.3.1 with SIGSEGV in gdk_window_object_get_type

Bug #1274419 reported by Imtiaz Rahi
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openjdk-7 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Eclipse kepler (4.3.1) won't start on Ubuntu 13.10 with openjdk-7-jdk:i386 version 7u51-2.4.4-0ubuntu0.13.10

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb72b6ab9, pid=2076, tid=3075765952
#
# JRE version: OpenJDK Runtime Environment (7.0_51) (build 1.7.0_51-b00)
# Java VM: OpenJDK Client VM (24.45-b08 mixed mode, sharing linux-x86 )
# Problematic frame:
# C [libgdk-x11-2.0.so.0+0x35ab9] gdk_window_object_get_type+0x5e9
#

Tags: eclipse
Revision history for this message
Imtiaz Rahi (imtiaz.rahi) wrote :
Revision history for this message
Piotr Jasiulewicz (pjasiulewicz) wrote :

Hi, exectly same problem, but with Oracle JVM.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fbc10193f52, pid=3123, tid=140445915776768
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgdk-x11-2.0.so.0+0x3bf52] gdk_window_object_get_type+0x5f2
#
# 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 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.
#

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in openjdk-7 (Ubuntu):
status: New → Confirmed
Revision history for this message
MeduZa (meduzapat) wrote :

I never got this error before, yesterday everything was working nice and smooth, this morning when I opened my Kepler I got this error, I attaching my crash report, looking for a workaround :(

Revision history for this message
Andreas Reichart (andreas-reichart) wrote :

Same error on Oracle 1.8.0-b132

Crash happens 1 second after the appearance of the the Workbench.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb7304ab9, pid=4982, tid=3076155072
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
# Java VM: Java HotSpot(TM) Client VM (25.0-b70 mixed mode linux-x86 )
# Problematic frame:
# C [libgdk-x11-2.0.so.0+0x35ab9] gdk_window_object_get_type+0x5e9

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.