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

Bug 340367

Summary: crashes with java exit code 1 on shared workspace after moving to new computer
Product: [Eclipse Project] Platform Reporter: Missing name <weltensturm>
Component: ResourcesAssignee: Platform-Resources-Inbox <platform-resources-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: aniefer, jamesblackburn+eclipse
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
workspace settings
none
window manager part x11 none

Description Missing name CLA 2011-03-17 15:50:16 EDT
Build Identifier: 20110218-0911

I am using a shared workspace between Linux and Windows 7 (both 64 bit). This worked fine for a while, until I moved to a new laptop (from 32 to 64 bit on Windows, Linux was 64), since then the program randomly crashes.

Eclipse itself was not moved, only the workspace. When I use a completely new one, it works perfectly well.

The error window says:

Java was started but returned exit code=1
C:\Windows\system32\javaw.exe
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar C:\Program Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-os win32
-ws win32
-arch x86_64
-showsplash
-launcher C:\Program Files\eclipse\eclipse.exe
-name Eclipse
--launcher.binary C:\Program Files\eclipse\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.2.R36x_v20101222\eclipse_1312.dll
-startup C:\Program Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-exitdata f08_5c
-product org.eclipse.epp.package.cpp.product
-vm C:\Windows\system32.javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar C:\Program Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar


Part of the console output:

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d93c4eb, pid=2908, tid=744

JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64 compressed oops)
Problematic frame:
V [jvm.dll+0x14c4eb]


Reproducible: Always

Steps to Reproduce:
I am not sure if these will work.
1. Set up Eclipse CDT on Windows x86 and create a Hello World project.
2. Set up Eclipse CDT on Windows x86_64 and select as workspace the one created in x86.
3. Try using the workspace normally, it crashes every time for me.
Comment 1 Missing name CLA 2011-03-17 15:59:38 EDT
Only appears to happen on Windows.
Comment 2 Missing name CLA 2011-03-18 10:38:34 EDT
Created attachment 191512 [details]
workspace settings

Cannot load workspace anymore on windows at all.
These are the settings (.metadata) for said workspace.
Comment 3 Andrew Niefer CLA 2011-03-18 13:12:16 EDT
(In reply to comment #0)
> Part of the console output:
> 
> A fatal error has been detected by the Java Runtime Environment:
> 
> EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d93c4eb, pid=2908,
> tid=744
> 
> JRE version: 6.0_24-b07
> Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64
> compressed oops)
> Problematic frame:
> V [jvm.dll+0x14c4eb]

Is there more to this output? Can you attach it here?
Comment 4 Missing name CLA 2011-03-18 13:15:38 EDT
(In reply to comment #3)
> (In reply to comment #0)
> > Part of the console output:
> > 
> > A fatal error has been detected by the Java Runtime Environment:
> > 
> > EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d93c4eb, pid=2908,
> > tid=744
> > 
> > JRE version: 6.0_24-b07
> > Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64
> > compressed oops)
> > Problematic frame:
> > V [jvm.dll+0x14c4eb]
> 
> Is there more to this output? Can you attach it here?

I can't since it now throws me an error directly when loading the workspace, but the log files are in the workspace settings attachment.
Comment 5 Andrew Niefer CLA 2011-03-18 13:45:46 EDT
There are a bunch of unrelated NPE errors in the log, I raised bug 340464 on the CDT.  If you can attach it there, they would likely be interested in "/X11 01/src/include/window_x11.cpp".

I'm moving this bug over to the platform since the root exception in the log here is 

org.eclipse.core.internal.dtree.ObjectNotFoundException: Tree element '/X11 01/src/main.cpp' not found.
        at org.eclipse.core.internal.dtree.AbstractDataTree.handleNotFound(AbstractDataTree.java:257)
        at org.eclipse.core.internal.dtree.DeltaDataTree.getData(DeltaDataTree.java:585)
        at org.eclipse.core.internal.dtree.DataDeltaNode.asBackwardDelta(DataDeltaNode.java:50)
        at org.eclipse.core.internal.dtree.NoDataDeltaNode.asBackwardDelta(NoDataDeltaNode.java:59)
        at org.eclipse.core.internal.dtree.NoDataDeltaNode.asBackwardDelta(NoDataDeltaNode.java:59)
        at org.eclipse.core.internal.dtree.DataDeltaNode.asBackwardDelta(DataDeltaNode.java:47)
        at org.eclipse.core.internal.dtree.DeltaDataTree.asBackwardDelta(DeltaDataTree.java:88)
        at org.eclipse.core.internal.dtree.DeltaDataTree.reroot(DeltaDataTree.java:816)
        at org.eclipse.core.internal.dtree.DeltaDataTree.reroot(DeltaDataTree.java:815)
        at org.eclipse.core.internal.dtree.DeltaDataTree.reroot(DeltaDataTree.java:792)
        at org.eclipse.core.internal.watson.ElementTree.immutable(ElementTree.java:517)
        at org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:688)
        at org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1503)
        at org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2134)
        at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:1883)
        at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:406)

This is during activation of org.eclipse.core.resources leading to java.lang.NoClassDefFoundError later.

I'm not sure what the native crash log would have been about.
Comment 6 Missing name CLA 2011-03-18 13:52:03 EDT
Created attachment 191532 [details]
window manager part x11

I don't know if it matters, but I was also using hard links to use the same file in more than one project.

And sorry, I've never been good at finding the section something belongs to.
Comment 7 James Blackburn CLA 2011-03-18 14:07:56 EDT
(In reply to comment #5)
> There are a bunch of unrelated NPE errors in the log, I raised bug 340464 on
> the CDT.  If you can attach it there, they would likely be interested in "/X11
> 01/src/include/window_x11.cpp".

This root exception is bug 149121. Can be caused by moving a workspace after a crash, for example.

*** This bug has been marked as a duplicate of bug 149121 ***
Comment 8 Missing name CLA 2011-03-21 20:16:32 EDT
Okay sorry, this has nothing to do with moving the files. It happens even with a clean extract (.eclipse folder deleted) and a new workspace, most when I am saving a new .cpp file. Now this only happens on 64 bit eclipse, 32 works so far.
A little unrelated: to work with 64 bit eclipse a 64 bit java installation is required, but the only way to install it is through Internet Explorer 64 Bit (with no hints to that at all), which is a little confusing.
Now I would appreciate it if somebody would tell me if I should reopen a new bug for that, reopen this one or post the information to bug 340464.
Comment 9 James Blackburn CLA 2011-03-22 05:01:29 EDT
(In reply to comment #8)
> Okay sorry, this has nothing to do with moving the files. It happens even with
> a clean extract (.eclipse folder deleted) and a new workspace, most when I am
> saving a new .cpp file. Now this only happens on 64 bit eclipse, 32 works so
> far.

That's a different issue, very likely: bug 333227.