Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Fatal error by Java runtime environment

Tags:

I am executing a junit test case

I got the following error,

A fatal error has been detected by the Java Runtime Environment:  Internal Error (classFileParser.cpp:3174), pid=2680, tid=2688    Error: ShouldNotReachHere()    JRE version: 6.0_18-b07    Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode windows-x86 ) 

Can any body please suggest the solution to resolve

like image 964
siri Avatar asked Mar 30 '10 05:03

siri


People also ask

How do I fix a fatal error in Java Runtime Environment?

Most of the users have fixed the similar issue by uninstall older versions of Java and installing latest version. You may refer to the link to uninstall the older versions of Java. Refer to the link to install the latest version of Java. You may also refer to the link and check.

What is fatal error in Java?

Fatal errors are errors such as native memory exhaustion, memory access errors, or explicit signals directed to the process.

What is fatal error in Oracle?

The fatal error log is created when a fatal error occurs. It contains information and the state obtained at the time of the fatal error. Note: The format of this file can change slightly in update releases.


1 Answers

I got the same problem, but with alot of googling I found the answer! See this page

Quote from the link:


# An unexpected error has been detected by Java Runtime Environment: # #  Internal Error (classFileParser.cpp:2924), pid=5364, tid=6644 #  Error: ShouldNotReachHere 
  1. That's because we are using Android's JUnit stub implementation. Go to Run -> Run As -> Run configurations again and in the recently created JUnit configuration Classpath's Bootstrap Entries remove Android Library
  2. Then Add Library, using Advanced... button, and add JRE System Library and JUnit 3
  3. Apply and Run

Try this, it worked for me.

like image 180
Fredrik Avatar answered Sep 23 '22 13:09

Fredrik