Skip to content

8355649: Missing ResourceMark in ExceptionMark::check_no_pending_exception#24896

Closed
lmesnik wants to merge 1 commit intoopenjdk:masterfrom
lmesnik:8355649
Closed

8355649: Missing ResourceMark in ExceptionMark::check_no_pending_exception#24896
lmesnik wants to merge 1 commit intoopenjdk:masterfrom
lmesnik:8355649

Conversation

@lmesnik
Copy link
Member

@lmesnik lmesnik commented Apr 26, 2025

I find during test development.
I don't think that separate regression test is needed here.


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-8355649: Missing ResourceMark in ExceptionMark::check_no_pending_exception (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24896

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 26, 2025

👋 Welcome back lmesnik! 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 Apr 26, 2025

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

8355649: Missing ResourceMark in ExceptionMark::check_no_pending_exception

Reviewed-by: jsjolen, 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 34 new commits pushed to the master 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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 26, 2025
@openjdk
Copy link

openjdk bot commented Apr 26, 2025

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

@openjdk openjdk bot added the hotspot hotspot-dev@openjdk.org label Apr 26, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 26, 2025

Webrevs

Copy link
Contributor

@johan-sjolen johan-sjolen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Leonid,

Where is the resource allocation? I can't find it :).

Thanks,
Johan

@lmesnik
Copy link
Member Author

lmesnik commented Apr 27, 2025

The print requires allocation.
As I understand caller should add it and not print() itself.

@johan-sjolen
Copy link
Contributor

The print requires allocation. As I understand caller should add it and not print() itself.

How do you know that it requires allocation?

@johan-sjolen
Copy link
Contributor

Here's the resource allocation:

st->print_cr("%s ", internal_name()); // klass.cpp:1006

And it comes with a small comment: // Caller needs ResourceMark

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 28, 2025
Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks okay. It is common to require ResourceMark around printing statements. And in here, we are going to fail with fatal, so VM is going down anyway.

@lmesnik
Copy link
Member Author

lmesnik commented Apr 28, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Apr 28, 2025

Going to push as commit af4388a.
Since your change was applied there have been 46 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 28, 2025
@openjdk openjdk bot closed this Apr 28, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 28, 2025
@openjdk
Copy link

openjdk bot commented Apr 28, 2025

@lmesnik Pushed as commit af4388a.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants