A fatal error has been detected by the Java Runtime Environment: Internal Error ; Error: ShouldNotReachHere()

别等时光非礼了梦想. 提交于 2019-12-02 22:04:51
jo_

I had the same problem when running "pure java junit test" inside an android dev project.

so the solution was to do the following in Eclipse:

  • Add the std JRE to "properties --> java build path --> libraries"
  • While running, In the "runconfiguration --> classpath" remove Android (leaving only std JRE)
danielad

Here is your relief for the problem :

I have a problem of running different versions of STS this morning, the application crash with the similar way as the question did.

Excerpt of my log file.

A fatal error has been detected by the Java Runtime Environment:
#a
#  SIGSEGV (0xb) at pc=0x00007f459db082a1, pid=4577, tid=139939015632640
#
# JRE version: 6.0_30-b12
# Java VM: Java HotSpot(TM) 64-Bit Server VM 
(20.5-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libsoup-2.4.so.1+0x6c2a1]  short+0x11

note that exception occured at # C [libsoup-2.4.so.1+0x6c2a1] short+0x11

Okay then little below the line :

R9 =0x00007f461829e550: <offset 0xa85550> in /usr/share/java/jdk1.6.0_30/jre/lib/amd64/server/libjvm.so at 0x00007f4617819000
R10=0x00007f461750f7c0 is pointing into the stack for thread: 0x00007f4610008000
R11=0x00007f459db08290: soup_session_feature_detach+0 in /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 at 0x00007f459da9c000
R12=0x0000000000000000 is an unknown value
R13=0x000000074404c840 is an oop
{method} 

This line tells you where the actual bug or crash is to investigate more on this crash issue please use below links to know more , but let continue the crash investigation and how i resolved it and the novelty of this bug :)

links ARE :

a fATAL ERROR JAVA THIS ONE IS GREAT LOTS OF USER!

a fATAL ERROR JAVA 2

Okay , after that here what i found out to casue of this case and why it happens a general advise.

  1. Most of the time ,check that if u have installed , updated recently on Ubunu and Windows there are libraries like libsoup in linux whihc were the casuse of my crash.
  2. Check also a new Hardware problem and try to investigate the Logfile which STS or Java generated and also syslog in linux by

    tail - f /var/lib/messages or some other file
    

    Then by carfully looking at those file the one you have crash log ... you can really solve the issue as follow .

sudo unlink /usr/lib/i386-linux-gnu/libsoup-2.4.so.1

or

sudo unlink /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1

Done !! Cheers!!

user3536529

I've had a similar problem.

Error Log:

EAX=0x08aef338
0x08aef338 is pointing to unknown location

EBX=0x7c5e7000
0x7c5e7000: in /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 at 0x7c558000

Fix:

unlink /usr/lib/i386-linux-gnu/libsoup-2.4.so.1

Just check to see what file you're actually running when you hit the run button. I had the same issue when I wrote a "public static void main" statement in a "non-main" file of the program. I even commented it out, but it wouldn't work. This link was very helpful for me.

I just had this error and solved it by using 'Run As' and choosing 'Android Application'.

Looks like a corrupt class file. Rebuild.

Change the workspace.

I don't know the reason but this worked for me..

Hope this helps to you as well !!

I had the same problem after adding main method in one of my classes in an Android project. I just right click on the project and run it as an Android project and then it worked again!

SahuNaz

I had faced the same issue. The command

sudo unlink /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1

was also not useful as it crashed my system network and not able to connect Wi-Fi or wired lan. Later i got the solution from here.

Adding line -Dorg.eclipse.swt.browser.DefaultType=mozilla at the end of eclipse.ini or org.eclipse.swt.browser.DefaultType=mozilla at the end of /eclipse/configuration/config.ini file solved the issue.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!