-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK11 Segmentation error vmState=0x000514ff #15364
Comments
Sometimes, the reduced and unreduced test does not reproduce. Just repeat it for some times. It will definitely crash (at least on our desktop and server). |
No problem reproducing the crash, which also occurs with jdk8. I also saw the following
|
@0xdaryl another one |
This is not a regression in 0.33. Reproducible on JDK8 back to at least 0.29. |
Original problem crashes during GVP. @hzongaro, could you add this to your list to investigate please? |
Ooops! I thought I had posted this comment yesterday. Anyway, I'm about to add a follow on post with more details. I took a quick look at this running in gdb. In that run I see the crash happening in a
|
Upon rerunning the test in gdb with
Setting a breakpoint in
Removing the redundant node results in |
As Daryl pointed out, this is a long-standing problem. It appears to require the Having said that, I think I know how to fix the problem, but it might take me a couple of days to write up the fix and test it out. I would rather not rush it in. |
Removing blocker and moving forward. |
Java -version output
Summary of problem
The following
Test.java
, which is reduced by us, crashes OpenJ9's JIT compilerDiagnostic files
By issuing
the following crash log is given:
Please also check openj9-bug-79.tar.gz for all the logs (jitdump, snap, etc.), the test (Test.java, Test.class), and the unreduced test (Test.java.orig).
Notice
The given
Test.java
(which is reduced by us) is always reproducible for us. If it is not reproducible for you, please useTest.java.orig
in the above link.This issue crashed with the same vmState as issue #15311 but different stack trace and different JDK version.
The text was updated successfully, but these errors were encountered: