-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8289838: ZGC: OOM before clearing all SoftReferences #10646
Conversation
👋 Welcome back eosterlund! A progress list of the required criteria for merging this PR into |
@fisk 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 26 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 |
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.
Lgtm.
@fisk this pull request can not be integrated into git checkout 8289838_soft_ref_trouble
git fetch https://git.openjdk.org/jdk master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
/integrate |
Going to push as commit 491d43c.
Your commit was automatically rebased without conflicts. |
Thanks for the reviews! |
should_clear_soft_references() in mainline ZGC is based purely on the cause of the GC, but the GC cause being used to catch that we need to clear soft references is asynchronous. Another GC could start an instant before it is requested, such as a metadata threshold GC for example. Then the metadata threshold GC will be used instead.
Even if the other async GC that was requested is also of the kind that requires soft references to be cleared, such as a concurrently requested _z_allocation_stall GC, it is possible that the async GC request is performed after a soft reference was created, after a concurrent thread requests a _z_allocation_stall GC, but before that GC has reached mark_start, implying that the sequence number will look like it already got to run an entire GC before throwing, while in fact it did not.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10646/head:pull/10646
$ git checkout pull/10646
Update a local copy of the PR:
$ git checkout pull/10646
$ git pull https://git.openjdk.org/jdk pull/10646/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10646
View PR using the GUI difftool:
$ git pr show -t 10646
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10646.diff