-
Notifications
You must be signed in to change notification settings - Fork 728
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
Crash in JIT with vmState=0x0002000f #13617
Comments
As per
Try now. Edit: Also did ub20x64-2 |
Thanks, I was about to ask that all machines be checked. We can't necessarily repeat the crashes and generate another core, we need core collection to work when the failures occur. |
First grinder for 10 test iterations passed, there is another one for 20: https://openj9-jenkins.osuosl.org/job/Grinder/257/ |
All jobs passed, running another grinder https://openj9-jenkins.osuosl.org/job/Grinder/258/ |
An occurrence at an internal JDK17
|
I downloaded artifacts (results and jvm) to The crash occur in
Based on registers content I suspect java stack for thread @0xdaryl FYI |
Haven't seen this for a while, closing. |
This may have happened again in an internal test |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.openjdk_x86-64_linux_Release/9 - ub18-x86-1
jdk_lang_1
-Xdump:system:none -Xdump:heap:none -Xdump:system:events=gpf+abort+traceassert+corruptcache -XX:-JITServerTechPreviewMessage -XX:-UseCompressedOops
jdk/modules/scenarios/automaticmodules/RunWithAutomaticModules.java
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk11_j9_sanity.openjdk_x86-64_linux_Release/9/openjdk_test_output.tar.gz
@AdamBrousseau there is a machine problem capturing the system core file, pls fix the machine.
The text was updated successfully, but these errors were encountered: