-
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
Recognize JNI local refs in JNINativeMethodFrames #18378
Conversation
There is a dependent change from GC side from @LinHu2016 to correctly mark slots returned based on vm supplied |
Changes LGTM. @fengxue-IS Can you include the below justification in the commit message?
|
Will we need to wait for the GC change before merging this PR? |
no, just need the GC changes to pass the test. |
First 8 JNI local refs are directly stored inside the J9SFJNINativeMethodFrame before allocating J9JNIReferenceFrame to store additional references. StackWalker should check if the object pushes from method frame is JNI local when walking O-Slots. Signed-off-by: Jack Lu <[email protected]>
jenkins test sanity amac jdk21 |
jenkins compile win jdk21 |
jenkins test sanity.openjdk,extended.openjdk amac jdk21 |
1 similar comment
jenkins test sanity.openjdk,extended.openjdk amac jdk21 |
Launching new PR builds on a different platform due to infra issues: jenkins test sanity,sanity.openjdk,extended.openjdk alinux jdk21 |
|
First 8 JNI local refs are directly stored inside the
J9SFJNINativeMethodFrame
before allocatingJ9JNIReferenceFrame
to store additional references. StackWalker should check if the object pushes from method frame is JNI local when walking O-Slots.Related: #17712
Signed-off-by: Jack Lu [email protected]