Best way on how to solve/debug JVM crash (SIGSEGV)

前端 未结 3 1113
别跟我提以往
别跟我提以往 2021-02-06 00:26

I\'m really lost and I don\'t know how to face and solve my problem. I have a piece of simple Java Code, which leads to a JVM crash:

#
# A fatal error has been d         


        
3条回答
  •  说谎
    说谎 (楼主)
    2021-02-06 01:03

    It looks like JDK bug JDK-6675699. According to the bug report, the fix for that bug has been backported to 8u74, 8u81 and 8u82.

    Note that (as of right now) the end-user focused Java Download Site offers 8u73 as the latest version. You can get 8u74 from the Java Developer Download Site.


    If updating to 8u74 doesn't solve the problem, then you should submit this to Oracle as a bug report. The likely diagnosis is that you are running code that is causing the JIT code compiler to crash when it attempt to compile / optimize it. That's what PhaseIdealLoop::idom_no_update is indicating.

    JDK-6675699 is for a specific JIT compiler bug. There could well be other JIT compiler bugs that have not been diagnosed. If you submit a new bug report, it could help the maintainers to track down those bugs. However, a bug report will only be useful to them if you can provide enough information to allow them to reproduce your bug.

    (Of course, it is also possible that the root cause is something completely different; e.g. something in your code 3rd party code that is corrupting JVM data structures that is causing the compiler to crash. But it would a huge coincidence for the corruptions to repeatably break the compiler ... and only the compiler.)


    UPDATE - According to these Release Notes, the version you actually need is Java SE 8u74-b32.

提交回复
热议问题