-
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
8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache #9724
8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache #9724
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
It would be good if this PR got reviewed and integrated soon. The number of |
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.
Looks good.
@tschatzl 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 43 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 |
Thanks @albertnetymk @kimbarrett for your reviews |
Going to push as commit f9bb367.
Your commit was automatically rebased without conflicts. |
Hi all,
can I have reviews for this wrong use of
G1CollectedHeap::heap_region_containing
inG1RemSet::clean_card_before_refine()
?If a card is evicted from the hot card cache it might also be located in an outdated (reclaimed) region (by Remark). So the call needs to explicitly consider that case and use
heap_region_containing_or_null
and appropriately check for that later.This is only an issue in debug mode, because while still this is kind of an illegal request, the return value will always be a valid
HeapRegion
instance as we never deallocate them.Testing: reproduced crashes with the given test case (1:5), no more crashes afterwards.
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9724/head:pull/9724
$ git checkout pull/9724
Update a local copy of the PR:
$ git checkout pull/9724
$ git pull https://git.openjdk.org/jdk pull/9724/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9724
View PR using the GUI difftool:
$ git pr show -t 9724
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9724.diff