-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8316319: Generational ZGC: The SoftMaxHeapSize might be wrong when CDS decreases the MaxHeapSize #15841
Conversation
…S decreases the MaxHeapSize
👋 Welcome back stefank! A progress list of the required criteria for merging this PR into |
@mrserb - thanks for reporting this bug! Do you want to test this patch in your test infra? |
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.
@stefank 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 36 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 |
Looking into the patch. |
Thanks for reviewing! |
Going to push as commit fe86263.
Your commit was automatically rebased without conflicts. |
Generational ZGC sets SoftMaxHeapSize to 90% of the MaxHeapSize if the user has not specified the maximum heap size with any of the available flags. Unfortunately, this break when CDS later on decreases the MaxHeapSize.
I propose that we solve this by moving the code that sets the SoftMaxHeapSize to the point after CDS and the GC has done its final tweaks to the MaxHeapSize.
This can be easily reproduced just by running:
java -XX:+UseZGC -XX:+ZGenerational -Xshare:dump -Xlog:gc+init -version
This wasn't caught in testing because our test infrastructure uses MaxRamPercentage to set the maximum heap size. I've manually verified that the patch fixes the issue and that SoftMaxHeapSize is set as expected.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15841/head:pull/15841
$ git checkout pull/15841
Update a local copy of the PR:
$ git checkout pull/15841
$ git pull https://git.openjdk.org/jdk.git pull/15841/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15841
View PR using the GUI difftool:
$ git pr show -t 15841
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15841.diff
Webrev
Link to Webrev Comment