-
Notifications
You must be signed in to change notification settings - Fork 208
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
8323086: Shenandoah: Heap could be corrupted by oom during evacuation #2114
8323086: Shenandoah: Heap could be corrupted by oom during evacuation #2114
Conversation
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
|
@earthling-amzn I removed the fix-request tag. |
I think the part of the missing background here (which would really be in fix-request) is that we have been running with this patch in GenShen for quite a while. So this is not really a new patch, it fixes an important corner case, and so I think it would be useful to have in current 17u (17.0.11). @GoeLin, can we still do it? @earthling-amzn should probably re-request with the much better fix-request. |
/approval request Please accept my apologies for the previously terse approval request. We discovered this issue almost two years ago during development of the generational mode for Shenandoah (which, at the time was more prone to out of memory errors during evacuation). Originally, it wasn't clear to us that the bug affected the upstream branch. We've been running this code in various internal customer test environments for the past two years. Additionally, we have nightly automated tests that run the latest Dacapo, Heapothesys, Extremem, SpecJBB1015, SpecJVM2008, and Diluvian benchmarks in both the release configuration, and a fastdebug configuration with GC stress flags enabled. |
@earthling-amzn |
@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 49 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. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@earthling-amzn |
/sponsor |
Going to push as commit cb3bd49.
Your commit was automatically rebased without conflicts. |
@shipilev @earthling-amzn Pushed as commit cb3bd49. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2114/head:pull/2114
$ git checkout pull/2114
Update a local copy of the PR:
$ git checkout pull/2114
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2114/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2114
View PR using the GUI difftool:
$ git pr show -t 2114
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2114.diff
Webrev
Link to Webrev Comment