-
Notifications
You must be signed in to change notification settings - Fork 714
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
j9mm.479 * ** ASSERTION FAILED ** at openj9/runtime/gc_glue_java/MarkingSchemeRootMarker.cpp:53: ((MM_StackSlotValidator(MM_StackSlotValidator::NOT_ON_HEAP, object, stackLocation, walkState).validate(_env))) #13369
Comments
Also observed at MacOS
|
@dmitripivkine fyi |
As mentioned above this is exactly the same issue as #13017, The problem seems is not limited to ARM platform @0xdaryl FYI |
@pshipton I can triage this if you like to have more information about frame where the bad o-slot is discovered and compare between Windows/Mac/Arm cases (I assuming system cores are available). These failures are identical including |
I found Windows build but there is artefacts stored |
If it helps the JIT team. |
I've not been able to reproduce the failures so far. |
I'll go ahead and close, we can reopen if seen again. |
Re-opening - I was able to reproduce the failure. |
Observed at JDK8
|
Failures like this on AArch64 may be #13507. I'm not saying that definitively, but it is a possiblity. That PR was just merged yesterday. |
So far I've seen failures on MacOS, but they haven't exhibited the O-Slot assertion failure symptom. Instead I've seen NullPointerExceptions like the following, which bears a strong resemblance to issue #13472. I don't know whether they are two different symptoms of the same problem or two distinct problems, so I'll continue to investigate.
|
Closing, as the original problem reported in this issue is a likely dup of #13180. Other issues encountered during the investigation seem to be tracked by other issues. |
JDK16 Windows build has same assertion error at
Test_openjdk16_j9_special.system_x86-64_windows_Personal/6/tapResults/
Re-run the Grinder
Edit: assigning this to 0.28 release since JDK16 head stream w/ ojdk_mh is used for JDK17 test.
Originally posted by @JasonFengJ9 in #13017 (comment)
There is a similar assertion at
aarch64_linux
#13017. Created this issue to track Windows platform as per #13017 (comment)The text was updated successfully, but these errors were encountered: