-
Notifications
You must be signed in to change notification settings - Fork 730
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
openjdk11_j9_extended.functional_ppc64le_linux_xl testOpenJ9DiagnosticsMXBean_1 Segmentation error vmState=0x00020002 #8019
Comments
@dmitripivkine can you pls take a look |
This crash occur because of |
I have result files downloaded, ask me where |
In order to discover module objects GC walks |
Looks like at the moment of crash module address is added to the hash table. So I guess module was collected right after creation but before added to hash table. We should double check there is no time when GC might occur |
This is a low reproduction rate (only reported once so far), and it's getting to be to late to make any more fixes in the 0.18 release, moving it out. |
Seems this won't be resolved for the 0.20 release, moving it forward. |
Seen at Adopt on https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_aarch64_linux/103/#showFailuresLink
Dumps: https://ibm.box.com/shared/static/xli15fximvjrc72tf7c4s4fmhhmd5wqh.gz |
@M-Davies @JasonFengJ9 Does this issue still occur? |
@DanHeidinga No, I don't recall such failure recently, also searched last ten Pipeline-Build-Test-All-11 builds in https://ci.eclipse.org/openj9 via TRSS and didn't have a hit. |
I'm running some grinders to verify but I don't think so unless you've seen it recently @archanaNogriya ? |
I'm going to close this now given the lack of reoccurrence. If it happens again, please comment here and the issue can be reopened |
Failure link
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_extended.functional_ppc64le_linux_xl_Nightly/8/tapResults/
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: