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
8253960: Memory leak in Java_java_lang_ClassLoader_defineClass0() #492
Conversation
👋 Welcome back zgu! A progress list of the required criteria for merging this PR into |
/label add core-libs |
@zhengyu123 |
@zhengyu123 |
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.
Thanks for catching this. Looks good.
@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 more 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 50 new commits pushed to the
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 |
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.
Look good!
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.
Should this be renamed to "Memory leak in Lookup.defineClass"? I don't think it impacts anything extending or using the ClassLoader.
/integrate |
@zhengyu123 Since your change was applied there have been 54 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 19219a9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The memory leak is quite obvious. Early return results 'body' not been released.
Test:
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/492/head:pull/492
$ git checkout pull/492