Community
Participate
Working Groups
# # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a99d997e1, pid=12532, tid=1089186144 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_04-b05 mixed mode) # Problematic frame: # J org.eclipse.jdt.internal.compiler.parser.Scanner.jumpOverMethodBody()V # --------------- T H R E A D --------------- Current thread (0x0000002affe87120): JavaThread "Java indexing" daemon [_thread_in_Java, id=12553] siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x0000002bde54ddb8 Registers: RAX=0x0000000000000846, RBX=0x0000000040eb9c30, RCX=0x0000000040eb9bd0, RDX=0x0000002adaa66ce0 RSP=0x0000000040eb9c70, RBP=0x0000002adaa66c0c, RSI=0x0000000000001569, RDI=0x0000000000000000 R8 =0x0000000000000001, R9 =0x0000002adaa79bb0, R10=0x000000000000000a, R11=0x0000000000000000 R12=0x0000002adaa66c40, R13=0x0000000000000000, R14=0x0000002adaa66ce0, R15=0x0000002affe87120 RIP=0x0000002a99d997e1, EFL=0x0000000000010297, CSGSFS=0x000000000000000b, ERR=0x0000000000000006 TRAPNO=0x000000000000000e (for full stack trace, send a request email to ahbln@yahoo.de) System: SuSE 9.2, KDE, AMD64, 1GB RAM, Sun SDK 1.5.0_03/1.5.0_04 installed (64bit), ATI Graphics card Eclipse 3.0 with SDK 1.4.2_08 runs stable!!
Please attach the full stack dump, zipped if it is big. I assume you are using the Eclipse 3.1 final release?
Created attachment 24753 [details] Error log file from originator Email from originator: yes, I downloaded the latest release 3.1 yesterday. After that, I imported a version 3.0 project and clicked on its properties (right mouse click on the project folder). A new "pop-up" window comes up for editing the project properties. Shortly after that, the IDE crashed two times. I deleted the whole 3.1 folder and re-installed, with the same effect. Version 3.0 runs with Sun Java 1.4.2_xx (32 bit), somewhat slowly, but totally stable :-)
From the dump file details, this looks like a VM error. The problematic frame is running a plain Java method with no native code. I suspect the Java 5 64 bit VM isn't as stable yet. It could be related to the complexity of the method being run (it's a >350 line method with some very deeply nested control flow). I suggest entering a bug against the VM provider.
See also bug 71987.
