-
Notifications
You must be signed in to change notification settings - Fork 144
8269594: assert(_handle_mark_nesting > 1) failed: memory leak: allocating handle outside HandleMark #173
Conversation
👋 Welcome back zgu! A progress list of the required criteria for merging this PR into |
@zhengyu123 The following label will be automatically applied to this pull request:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. I think it's worth fixing because the Handles could leak without this assert in production, and that could be really hard to diagnose.
@zhengyu123 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:
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 4 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me as well. I also ran into this assert while working on #149 [1] (when testing with ZGC)
@coleenp @JornVernee Thanks! |
/integrate |
Going to push as commit 4b4bef4.
Your commit was automatically rebased without conflicts. |
@zhengyu123 Pushed as commit 4b4bef4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I would like to fix this assertion in jdk17. It was caught in Shenandoah nightly test and hard to reproduce, but fix is simple and low risk.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17 pull/173/head:pull/173
$ git checkout pull/173
Update a local copy of the PR:
$ git checkout pull/173
$ git pull https://git.openjdk.java.net/jdk17 pull/173/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 173
View PR using the GUI difftool:
$ git pr show -t 173
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk17/pull/173.diff