-
Notifications
You must be signed in to change notification settings - Fork 116
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
8335409: Can't allocate and retain memory from resource area in frame::oops_interpreted_do oop closure after 8329665 #942
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
@shipilev This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 6 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
This backport pull request has now been updated with issue from the original commit. |
|
/approval request This fixes the regression introduced by JDK-8329665, which added ResourceMark in frame::oops_interpreted_do. Patch does not apply cleanly to jdk21u-dev, needs more adjustments, see PR. All tests pass. Risk is low-medium: touches a frequent path, was in mainline for 6 weeks, is being released in JDK 23 as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
Thanks! /integrate |
Going to push as commit db914b7.
Your commit was automatically rebased without conflicts. |
This fixes the regression introduced by JDK-8329665, which added
ResourceMark
inframe::oops_interpreted_do
. This is not really correct, as closures we call with that method can do resource allocations. The patch avoids this problem by cleanly allocating on C heap.The mainline patch wants
has_valid_mask
infrastructure added as part of JDK-8315954. That patch has implications for Graal, and have unresolved bug tail. Therefore, I just picked up relevant infra hunks here.Additional testing:
all
all
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/942/head:pull/942
$ git checkout pull/942
Update a local copy of the PR:
$ git checkout pull/942
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/942/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 942
View PR using the GUI difftool:
$ git pr show -t 942
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/942.diff
Webrev
Link to Webrev Comment