Skip to content

Conversation

@jsikstro
Copy link
Member

@jsikstro jsikstro commented Nov 13, 2025

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:

  • Oracle's tier1-3

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-8371783: Refactor GCCause in VM_CollectForMetadataAllocation (Enhancement - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28287

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 13, 2025

👋 Welcome back jsikstro! 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 Nov 13, 2025

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

@openjdk
Copy link

openjdk bot commented Nov 13, 2025

@jsikstro 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.

@openjdk openjdk bot added the rfr Pull request is ready for review label Nov 13, 2025
@mlbridge
Copy link

mlbridge bot commented Nov 13, 2025

Webrevs

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