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
8231454: File lock in Windows on a loaded jar due to a leak in Introspector::getBeanInfo #647
Conversation
👋 Welcome back serb! A progress list of the required criteria for merging this PR into |
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.
@mrserb 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 129 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 |
/integrate |
@mrserb Since your change was applied there have been 154 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 2ee2b4a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
java.beans.Introspector is using a new cache mechanism since Java9 in com.sun.beans.introspect.ClassInfo::CACHE which uses a SoftReference cache over the class, which makes the class "leak", unless clearing the cache manually or collecting the SoftReference by the GC.
Note that this is not a pure "leak", because the SoftReference will be collected if there is no enough memory on the system, but if the heap is big enough then all objects referenced from the cached class will be in the memory.
The class has a reference to the ClassLoader, and If the soft reference to the class is not collected by the GC, then the ClassLoader cannot be unloaded and this block the jar file removing.
The solution is to update the implementation of Introspector.flushCaches()/flushFromCaches(Class) to clear the whole cache or the cache for the specific class.
Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/647/head:pull/647
$ git checkout pull/647