This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
8345750: Shenandoah: Test TestJcmdHeapDump.java#aggressive intermittent assert(gc_cause() == GCCause::_no_gc) failed: Over-writing cause #237
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was not a clean backport, the conflicts were trivial to resolve. This addresses a fairly critical issue where in a mistimed heap dump may cause heap corruption or vm crashes for Shenandoah GC.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk23u.git pull/237/head:pull/237
$ git checkout pull/237
Update a local copy of the PR:
$ git checkout pull/237
$ git pull https://git.openjdk.org/jdk23u.git pull/237/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 237
View PR using the GUI difftool:
$ git pr show -t 237
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk23u/pull/237.diff
Using Webrev
Link to Webrev Comment