8259627: Potential memory leaks in JVMTI after JDK-8227745 #87
8259627: Potential memory leaks in JVMTI after JDK-8227745 #87
Conversation
👋 Welcome back rrich! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
@reinrich 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 9 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 |
/integrate |
@reinrich Since your change was applied there have been 13 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 72be1e2. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is the jdk16u backport of the fix for JDK-8259627. The original patch applies cleanly without modification.
The fix passed our CI testing: JCK and JTREG, also in Xcomp mode, SPECjvm2008, SPECjbb2015, Renaissance Suite,
SAP specific tests with fastdebug and release builds on all platforms
Progress
Issue
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk16u pull/87/head:pull/87
$ git checkout pull/87
To update a local copy of the PR:
$ git checkout pull/87
$ git pull https://git.openjdk.java.net/jdk16u pull/87/head