Community
Participate
Working Groups
Eclipse fails to start because of jvm crash. This issue is similar to 116697 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=116697). Guess this might be related to eclipse configuration corruption(?) because eclipse however starts without problems with '-clean' option. This happens in two different workspaces, unfortunately i do not know what triggers such behavior. VM Arguments: java_command: D:\Applications\eclipse\startup.jar -os win32 -ws win32 -arch x86 -launcher D:\Applications\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata edc_70 -vm C:\WINDOWS\system32\javaw.exe -vmargs -jar D:\Applications\eclipse\startup.jar Launcher Type: SUN_STANDARD Environment Variables: JAVA_HOME=c:\Program Files\jdk150\ PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\Wireless\Bin\;c:\Program Files\jdk150\bin;d:\applications\util;d:\applications\ruby\bin USERNAME=akorobov OS=Windows_NT PROCESSOR_IDENTIFIER=x86 Family 6 Model 13 Stepping 8, GenuineIntel Stack trace : # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_FLT_STACK_CHECK (0xc0000092) at pc=0x00ad0758, pid=3692, tid=2532 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode, sharing) # Problematic frame: # v ~RuntimeStub::load_klass_patching Runtime1 stub # --------------- T H R E A D --------------- Current thread (0x003543b8): JavaThread "main" [_thread_in_Java, id=2532] siginfo: ExceptionCode=0xc0000092, ExceptionInformation=0x00000000 0x0006dca0 Registers: EAX=0xffffffff, EBX=0x0006dd28, ECX=0x22b6df90, EDX=0x0000000d ESP=0x0006dca0, EBP=0x0006dd78, ESI=0xffffffff, EDI=0x00000000 EIP=0x00ad0758, EFLAGS=0x00010206 Top of Stack: (sp=0x0006dca0) 0x0006dca0: 0006dcb4 0006dce0 00a729cf 00000000 0x0006dcb0: 00a76449 00002000 00000000 22b6dff8 0x0006dcc0: 22b6dfb0 0006dcc4 2aa9db9c 0006dcf4 0x0006dcd0: 2b2b6e08 00000000 2b2b69e8 0006dce8 0x0006dce0: ffff1372 ffff4020 ffffffff 00a7b27f 0x0006dcf0: 01f7001b 00000000 ffff0023 00000000 0x0006dd00: 0006f05c 001b003b 02020000 f0540000 0x0006dd10: 00000000 000000d0 1372e868 00000000 Instructions: (pc=0x00ad0758) 0x00ad0748: 83 ec 6c dd 34 24 9b d9 24 24 83 ec 40 dd 1c 24 0x00ad0758: dd 5c 24 08 dd 5c 24 10 dd 5c 24 18 dd 5c 24 20 Stack: [0x00030000,0x00070000), sp=0x0006dca0, free space=247k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) v ~RuntimeStub::load_klass_patching Runtime1 stub J java.io.DataInputStream.readUnsignedShort()I J java.io.DataInputStream.readUTF(Ljava/io/DataInput;)Ljava/lang/String; J java.io.DataInputStream.readUTF()Ljava/lang/String; v ~RuntimeStub::alignment_frame_return Runtime1 stub j org.eclipse.core.internal.resources.MarkerReader_3.read(Ljava/io/DataInputStream;Z)V+14 j org.eclipse.core.internal.resources.MarkerReader.read(Ljava/io/DataInputStream;Z)V+16 j org.eclipse.core.internal.resources.MarkerManager.restoreFromSave(Lorg/eclipse/core/resources/IResource;Z)V+120 j org.eclipse.core.internal.resources.MarkerManager.restore(Lorg/eclipse/core/resources/IResource;ZLorg/eclipse/core/runtime/IProgressMonitor;)V+3 j org.eclipse.core.internal.resources.SaveManager.restoreMarkers(Lorg/eclipse/core/resources/IResource;ZLorg/eclipse/core/runtime/IProgressMonitor;)V+166 j org.eclipse.core.internal.resources.SaveManager.restore(Lorg/eclipse/core/runtime/IProgressMonitor;)V+103 j org.eclipse.core.internal.resources.SaveManager.startup(Lorg/eclipse/core/runtime/IProgressMonitor;)V+2 j org.eclipse.core.internal.resources.Workspace.startup(Lorg/eclipse/core/runtime/IProgressMonitor;)V+186 j org.eclipse.core.internal.resources.Workspace.open(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+117 j org.eclipse.core.resources.ResourcesPlugin.startup()V+45 j org.eclipse.core.internal.compatibility.PluginActivator.start(Lorg/osgi/framework/BundleContext;)V+43
*** This bug has been marked as a duplicate of 116697 ***
This problem reappeared with the same stack trace in 3.2m5(which is expected since bug has not been yet fixed). The problem seems to be caused by some workspace configuration and can be fixed by re-recating workspace from scratch . Recreating workspace is quite painful. If the problem cannot be fixed at the moment is there any workaround, i.e. deleting/re-recreating config files causing crash?
Here's workarond suggestion by Patrick Palmen : "I found a (not perfect) workaround: Delete the file ".metadata\.plugins\org.eclipse.core.resources\.safetable\org.eclipse.co re.resources" in your workspace. Eclipse will start fine and remembers most of your settings. Unfortunately Eclipse forgets all your projects! So I have to Re-Import all of them from my projects-folder (I use to keep the project files outside my workspace) every morning." The other alternative is to backup/restore whole workspace, i.e. create brand new workspace, import all the projects while keeping projects code and eclipse files(.project, etc) outside of workspace, make sure workspace does not have this issue, [periodically] create a backup copy of workspace, restore workspace from backup when this problem occurs.
This is a VM bug.
*** Bug 132448 has been marked as a duplicate of this bug. ***
