Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330476

Summary: Java fatal error opening workspace
Product: [Eclipse Project] Platform Reporter: Ken Tomazin <ktomazin>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: accountarbit109, grant_gayed, hceylan, hleong25, kenneth.lloyd, kresten+eclipse, remy.suen
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
hs_err_pid file
none
log file per your request
none
Fatal crash after selecting new workspace none

Description Ken Tomazin CLA 2010-11-17 11:49:57 EST
Build Identifier: 20100917-0705

The JVM is crashing while attempting to open a new workspace.  I've found that some of the workspaces open when I move them from a subdirectory off my HOME  directory to my HOME directory.  I am running on Fedora Release 13 64 bit.  The following is printed to stdout:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000034bbe0d660, pid=3557, tid=139815447541520
#
# JRE version: 6.0_22-b04
# Java VM: Java HotSpot(TM) 64-Bit Server VM (17.1-b03 mixed mode linux-amd64 )
# Problematic frame:
# C  [libgobject-2.0.so.0+0xd660]  g_object_get_qdata+0x20
#
# An error report file with more information is saved as:
# /home/ktomazin/apps/eclipse/hs_err_pid3557.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


Reproducible: Always

Steps to Reproduce:
1. Open a workspace which is located in a subdirectory (e.g. $HOME/workspaces/workspace1
2. Crash
3.
Comment 1 Paul Webster CLA 2010-11-17 11:52:30 EST
Please attach the /home/ktomazin/apps/eclipse/hs_err_pid3557.log

PW
Comment 2 Ken Tomazin CLA 2010-11-17 11:53:21 EST
Created attachment 183317 [details]
hs_err_pid file
Comment 3 Ken Tomazin CLA 2010-11-17 16:09:45 EST
I was assuming that this was more of a jdk bug than an eclipse bug, but I just backed off to galileo-SR2 and it works fine there so it seems to be an eclipse problem.
Comment 4 Ken Tomazin CLA 2010-11-17 16:11:17 EST
Created attachment 183348 [details]
log file per your request
Comment 5 Grant Gayed CLA 2011-04-14 15:34:30 EDT
*** Bug 316710 has been marked as a duplicate of this bug. ***
Comment 6 Grant Gayed CLA 2011-04-14 16:01:03 EDT
*** Bug 342518 has been marked as a duplicate of this bug. ***
Comment 7 Henry CLA 2011-04-20 17:15:03 EDT
I am also having this issue all of a sudden.  I have Eclipse 3.5 installed, but wanted to use Eclipse 3.6 for a class I am taking.  I have then installed some plugins, and been using it couple times a week for about ~2 weeks.  Now I'm trying to create a new workspace for another class, I get a fatal error after selecting a new workspace.  I tried to copy the old workspace to a new location and see if that worked, but it still gave a fatal crash.  I went back to Eclipse 3.5 and created a new workspace and that worked (.metadata directory is created).  I would exit Eclipse 3.5 and open Eclipse 3.6 with the newly made workspace and it crashes.

I will attach hs_err_pid14774.log
Comment 8 Henry CLA 2011-04-20 17:16:23 EDT
Created attachment 193757 [details]
Fatal crash after selecting new workspace

I am also having this issue all of a sudden.  I have Eclipse 3.5 installed, but
wanted to use Eclipse 3.6 for a class I am taking.  I have then installed some
plugins, and been using it couple times a week for about ~2 weeks.  Now I'm
trying to create a new workspace for another class, I get a fatal error after
selecting a new workspace.  I tried to copy the old workspace to a new location
and see if that worked, but it still gave a fatal crash.  I went back to
Eclipse 3.5 and created a new workspace and that worked (.metadata directory is
created).  I would exit Eclipse 3.5 and open Eclipse 3.6 with the newly made
workspace and it crashes.
Comment 9 Henry CLA 2011-04-21 13:45:21 EDT
I think I found a workaround.  

Here is my environment:
- Linux OS (Ubuntu)
- One good workspace that was created and opened through Eclipse 3.6 (WS36)
- One workspace that was created through Eclipse 3.5 (WS35)

Case #1
Open WS35 in Eclipse 3.6 will cause fatal error

Case #2 (workaround)
Open WS36 in Eclipse 3.6, then switch workspace to WS35, and it opens.

Case #3 (new workspace workaround)
Open a new workspace with Eclipse 3.6, fatal error.  So I opened a good workspace (WS36), then switch workspace, then create a new workspace, this works.
Comment 10 Henry CLA 2011-04-21 13:56:35 EDT
I removed all the workspace's from the Eclipse "startup and shutdown" menu, so I can have a clean list of workspaces.  I then restarted Eclipse and pointed to a good workspace, and fatal error.  So I opened the default workspace (/home/$user/workspace) and it opened.  I switched to another workspace workaround, and I was able to get into the previous workspace.

I think there's something going on with the splash screen workspace opener.  Maybe a variable not being set?
Comment 11 Grant Gayed CLA 2013-06-26 16:31:21 EDT
Closing as a duplicate of bug 317763.  Note that its duplicate bug 383189 is marked fixed for 4.3 (released today).

*** This bug has been marked as a duplicate of bug 317763 ***