Skip to content

8368152: Shenandoah: Incorrect behavior at end of degenerated cycle#241

Closed
earthling-amzn wants to merge 1 commit intoopenjdk:masterfrom
earthling-amzn:fix-degen-brownout-25u
Closed

8368152: Shenandoah: Incorrect behavior at end of degenerated cycle#241
earthling-amzn wants to merge 1 commit intoopenjdk:masterfrom
earthling-amzn:fix-degen-brownout-25u

Conversation

@earthling-amzn
Copy link

@earthling-amzn earthling-amzn commented Sep 24, 2025

Not clean, but conflict was trivial to resolve.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • JDK-8368152 needs maintainer approval
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8368152: Shenandoah: Incorrect behavior at end of degenerated cycle (Bug - P4 - Approved)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u.git pull/241/head:pull/241
$ git checkout pull/241

Update a local copy of the PR:
$ git checkout pull/241
$ git pull https://git.openjdk.org/jdk25u.git pull/241/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 241

View PR using the GUI difftool:
$ git pr show -t 241

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/241.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 24, 2025

👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Sep 24, 2025

@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:

8368152: Shenandoah: Incorrect behavior at end of degenerated cycle

Reviewed-by: kdnilsen, phh

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 master branch:

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 /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot changed the title Backport f36c33c86df0400d2155bfadd9a6b5ea56743133 8368152: Shenandoah: Incorrect behavior at end of degenerated cycle Sep 24, 2025
@openjdk
Copy link

openjdk bot commented Sep 24, 2025

This backport pull request has now been updated with issue from the original commit.

@openjdk openjdk bot added backport Port of a pull request already in a different code base rfr Pull request is ready for review labels Sep 24, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 24, 2025

Webrevs

Copy link
Member

@phohensee phohensee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolution in degen_event_message() looks ok.

@openjdk
Copy link

openjdk bot commented Sep 29, 2025

⚠️ @earthling-amzn This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@earthling-amzn
Copy link
Author

/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.

@openjdk
Copy link

openjdk bot commented Oct 1, 2025

@earthling-amzn
8368152: The approval request has been created successfully.

@openjdk openjdk bot added approval Requires approval; will be removed when approval is received ready Pull request is ready to be integrated and removed approval Requires approval; will be removed when approval is received labels Oct 1, 2025
@earthling-amzn
Copy link
Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Oct 6, 2025
@openjdk
Copy link

openjdk bot commented Oct 6, 2025

@earthling-amzn
Your change (at version ed32b37) is now ready to be sponsored by a Committer.

@shipilev
Copy link
Member

shipilev commented Oct 7, 2025

/sponsor

@openjdk
Copy link

openjdk bot commented Oct 7, 2025

Going to push as commit ac9a03a.
Since your change was applied there have been 34 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 7, 2025
@openjdk openjdk bot closed this Oct 7, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Oct 7, 2025
@openjdk
Copy link

openjdk bot commented Oct 7, 2025

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Port of a pull request already in a different code base integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

4 participants