8335409: Can't allocate and retain memory from resource area in frame::oops_interpreted_do oop closure after 8329665

[pchilano]

Hi all,

This pull request contains a backport of commit 7ab96c74 from the openjdk/jdk repository.

The commit being backported was authored by Patricio Chilano Mateo on 10 Jul 2024 and was reviewed by David Holmes, Thomas Stuefe, Coleen Phillimore and Aleksey Shipilev.

Thanks

---

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-8335409: Can't allocate and retain memory from resource area in frame::oops_interpreted_do oop closure after 8329665 (Bug - P2)

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 20185

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back pchilanomate! A progress list of the required criteria for merging this PR into jdk23 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@pchilano 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:

8335409: Can't allocate and retain memory from resource area in frame::oops_interpreted_do oop closure after 8329665

Reviewed-by: shade

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 2 new commits pushed to the jdk23 branch:

• 908d1e9: 8336259: Wrong link to stylesheet.css in JavaDoc API documentation
• fd38606: 8325369: @sealedGraph: Bad link to image for tag on nested classes

Please see this link for an up-to-date comparison between the source branch of this pull request and the jdk23 branch.
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 jdk23 branch, type /integrate in a new comment.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@pchilano The following label will be automatically applied to this pull request:

• hotspot

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.

[mlbridge]

Webrevs

• 00: Full (ea7b13cc)

[pchilano]

Thanks for the review @shipilev!
/integrate

[openjdk]

Going to push as commit d7b7c17.
Since your change was applied there have been 3 commits pushed to the jdk23 branch:

• 5162e1a: 8334653: ISO 4217 Amendment 177 Update
• 908d1e9: 8336259: Wrong link to stylesheet.css in JavaDoc API documentation
• fd38606: 8325369: @sealedGraph: Bad link to image for tag on nested classes

Your commit was automatically rebased without conflicts.

[openjdk]

@pchilano Pushed as commit d7b7c17.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.