Skip to content

8365055: G1: Merge Heap Roots phase incorrectly clears young gen remembered set every time #26695

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

tschatzl
Copy link
Contributor

@tschatzl tschatzl commented Aug 8, 2025

Hi all,

please review this fix to G1 heap root merging that cleared the young gen remembered set multiple times (for every merging) and overwriting the most recent statistics for the number of young gen cards.

The latter is probably the more problematic, as it directly impacts young gen sizing statistics, potentially making young gen too large.

The fix is to move the two statements to the proper place - get current number of young gen cards at startup, clear the young gen remset when starting a new collection set - we do not need to do that earlier after all. Additionally we can add some (superfluous?) verification that during GC we really do not add to the young gen remset.

Testing: tier1-5

Thanks,
Thomas


Progress

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

Issue

  • JDK-8365055: G1: Merge Heap Roots phase incorrectly clears young gen remembered set every time (Bug - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26695

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26695.diff

Using Webrev

Link to Webrev Comment

Hi all,

  please review this fix to G1 heap root merging that cleared the young gen remembered set multiple times (for every merging) and overwriting the most recent statistics for the number of young gen cards.

The latter is probably the more problematic, as it directly impacts young gen sizing statistics, potentially making young gen too large.

Testing: tier1-5

Thanks,
  Thomas
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 8, 2025

👋 Welcome back tschatzl! 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 Aug 8, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk bot changed the title 8365055 8365055: G1: Merge Heap Roots phase incorrectly clears young gen remembered set every time Aug 8, 2025
@openjdk
Copy link

openjdk bot commented Aug 8, 2025

@tschatzl The following label will be automatically applied to this pull request:

  • hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@tschatzl tschatzl marked this pull request as ready for review August 8, 2025 12:56
@openjdk openjdk bot added the rfr Pull request is ready for review label Aug 8, 2025
@mlbridge
Copy link

mlbridge bot commented Aug 8, 2025

Webrevs

* move that G1Policy member to G1CollectedHeap as it's used to verify stuff in G1CollectedHeap (and not used elsewhere anyway)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-gc [email protected] rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

1 participant