-
Notifications
You must be signed in to change notification settings - Fork 720
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
JDK17 Segmentation error vmState=0x00020019 #15592
Comments
The reason for triggering assertions is heap corruption most likely:
This assertion is triggered in Object Allocation path. There is attempt to get memory from Memory Pool. The problem is Memory Pool expects to discover Linked Free Header at the next list element location (aka Dead Object) but it is not there.
Scavenger expects object at Crash is caused by heap corruption as well:
Most likely all three PRs (this, #15474, #15575) are manifestations of the same problem. @0xdaryl FYI |
I can reproduce this easily with 0.33 but not with 0.32, so it could be a new problem. I'll take a closer look. As @dmitripivkine said, it might be the same problem as #15474 and #15575. |
Duplicate of #15474 |
Fixed by pull request #15870. |
Java -version output
Summary of problem
This test is a bit triky. It looks quite similar (see
vMeth
) to the test in #15575 (seevMeth1
) and #15474 (seevMeth1
). But this time we can trigger a different crash, even though undeterministic and a bit similar to them.Also a JIT bug (cannot reproduce with Xint).
Diagnostic files
By issuing
the following crash log is given (the stack trace is similar to but different from 15474):
But note, this crash does not always happen. You sometimes trigger the same crash as 15575, sometimes a different assertion failure like
You may try it for several times.
You can also try the unreduced test in openj9-bug-110.tar.gz. But it is not deterministic, either. This zip contains all the logs (core, snap, etc.), the reduced test (Test.java, Test.class), and unreduced (Test.java.orig, FuzzerUtils.java).
The text was updated successfully, but these errors were encountered: