8371783: Refactor GCCause in VM_CollectForMetadataAllocation #28287
+11
−9
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.
Hello,
We should improve how we use and set GCCause in VM_CollectForMetadataAllocation to make it more clear when reading the code what is going on.
When constructing a VM_CollectForMetadataAllocation operation, we pass in a GCCause, which is not always the cause that is used, since we might also have to clear soft references as a last resort if earlier collection attemps is not enough to free up memory.
The GCCauseSetter at the start of this operation is also redundant as subsequent calls to initiate a GC set the cause themselves.
Testing:
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28287/head:pull/28287$ git checkout pull/28287Update a local copy of the PR:
$ git checkout pull/28287$ git pull https://git.openjdk.org/jdk.git pull/28287/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28287View PR using the GUI difftool:
$ git pr show -t 28287Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28287.diff
Using Webrev
Link to Webrev Comment