8368152: Shenandoah: Incorrect behavior at end of degenerated cycle#241
8368152: Shenandoah: Incorrect behavior at end of degenerated cycle#241earthling-amzn wants to merge 1 commit intoopenjdk:masterfrom
Conversation
Reviewed-by: kdnilsen, ysr
|
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
|
@earthling-amzn 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 32 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
This backport pull request has now been updated with issue from the original commit. |
phohensee
left a comment
There was a problem hiding this comment.
Resolution in degen_event_message() looks ok.
|
|
|
/approval request This change fixes an error that causes the generational mode for Shenandoah to run back-to-back degenerated and full GCs without raising an out-of-memory error as expected. More importantly, it fixes an error that causes other Shenandoah modes to run a full gc unconditionally after every degenerated cycle (making a bad situation worse). We have tested this fix on jtreg tiers 1-3 and on various benchmarks: dacapo, specjvm, specjbb, extremem, and renaissance. |
|
@earthling-amzn |
|
/integrate |
|
@earthling-amzn |
|
/sponsor |
|
Going to push as commit ac9a03a.
Your commit was automatically rebased without conflicts. |
|
@shipilev @earthling-amzn Pushed as commit ac9a03a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Not clean, but conflict was trivial to resolve.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u.git pull/241/head:pull/241$ git checkout pull/241Update a local copy of the PR:
$ git checkout pull/241$ git pull https://git.openjdk.org/jdk25u.git pull/241/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 241View PR using the GUI difftool:
$ git pr show -t 241Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/241.diff
Using Webrev
Link to Webrev Comment