-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8351921: G1: Pinned regions with pinned objects only reachable by native code crash VM #24060
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
8351921: G1: Pinned regions with pinned objects only reachable by native code crash VM #24060
Conversation
|
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
|
@tschatzl 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 24 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
walulyai
left a comment
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.
Looks good!
Nits:
* typos
|
Thanks @albertnetymk @walulyai for your reviews /integrate |
|
Going to push as commit 558c015.
Your commit was automatically rebased without conflicts. |
Hi all,
please review this fix for a crash in G1 where it tries to reclaim a pinned region that does not have any reference visible to the VM any more and there are no other reachable pinnable objects in the same region. This can happen e.g. when JNI code is the only holder for a reference.
This has been reported this in a real application, but the attached test case (that uses WhiteBox to simulate a lone pinnable object in a region where the GC does not have a reference any more) shows the principle as well.
The solution involves unconditionally adding pinned regions in the collection set to the set of evacuation failed regions, instead of only doing that when G1 first encounters a reachable pinnable object in that pinned region.
Testing: gha, tier1-5
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24060/head:pull/24060$ git checkout pull/24060Update a local copy of the PR:
$ git checkout pull/24060$ git pull https://git.openjdk.org/jdk.git pull/24060/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24060View PR using the GUI difftool:
$ git pr show -t 24060Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24060.diff
Using Webrev
Link to Webrev Comment