New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8258077: Using -Xcheck:jni can lead to a double-free after JDK-8193234 #43
Conversation
|
This backport pull request has now been updated with issue from the original commit. |
/issue add JDK-8259446 |
@hseigel |
/integrate |
@hseigel This PR has not yet been marked as ready for integration. |
@hseigel This change now passes all automated pre-integration checks. 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 2 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
|
Thanks Coleen, for the review! /integrate |
@hseigel Since your change was applied there have been 2 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit b7b2f61. |
Thanks for doing the backport Harold! |
The original bug fix patch applied cleanly and included regression tests. After applying the patch to a JDK-16u repo, the fix was regression tested by running Mach5 tiers 1 and 2 on Linux, Windows, and Mac OS, and running tiers 3-5 on Linux x64.
Progress
Issues
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk16u pull/43/head:pull/43
$ git checkout pull/43