Recently we upgraded our java version to latest java version which is 1.8. We have configured all our existing work space in 1.7 earlier, now upgraded the version to 1.8 , after that we see multiple times eclipse was crashed. There is no pattern in it,sometimes its crashing immediately but some times during debug. We see following error in logs
Problem:
This is known issue with Java 1.8 compiler with windows(JDK-8154831).
Solution:
We can add following JVM argument in eclipse.ini as a workaround for this problem. We can find eclipse.ini in eclipse installation directory.
A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005dcdc8df, pid=8652, tid=0x0000000000001e64 # # JRE version: Java(TM) SE Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.92-b14 mixed mode windows-amd64 compressed oops) # Problematic frame: # V [jvm.dll+0x4bc8df] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # --------------- T H R E A D --------------- Current thread (0x0000000014b38000): JavaThread "C2 CompilerThread0" daemon [_thread_in_native, id=7780, stack(0x00000000164f0000,0x00000000165f0000)] siginfo: ExceptionCode=0xc0000005, reading address 0x0000000000000008 Registers: RAX=0x0000000000000000, RBX=0x0000000000000000, RCX=0x000000001a8a37c0, RDX=0x0000000000001000 RSP=0x00000000165ebd10, RBP=0x0000000017019d30, RSI=0x000000001a8a37c0, RDI=0x00000000165ec240
Problem:
This is known issue with Java 1.8 compiler with windows(JDK-8154831).
Solution:
We can add following JVM argument in eclipse.ini as a workaround for this problem. We can find eclipse.ini in eclipse installation directory.
-XX:CompileCommand=exclude,org.eclipse.jdt.internal.compiler.parser.TypeConverter::*
0 Comments
Post a Comment