[
https://issues.apache.org/jira/browse/FLINK-16245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047288#comment-17047288
]
Guowei Ma commented on FLINK-16245:
-----------------------------------
This means that there would still be some object leak, but the cost will be
much smaller because only one delegate ClassLoader might be leaked if the user
does not clean up the context class loader.
> Use a delegating classloader as the user code classloader to prevent class
> leaks.
> ---------------------------------------------------------------------------------
>
> Key: FLINK-16245
> URL: https://issues.apache.org/jira/browse/FLINK-16245
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Stephan Ewen
> Priority: Critical
> Labels: usability
> Fix For: 1.11.0
>
>
> As reported in FLINK-11205, a reference to the user-code ClassLoader can be
> held by some libraries, causing class leaks.
> One way to circumvent this class leak is if the ClassLoader that we set as
> the user-code ClassLoader is a delegating ClassLoader to the real class
> loader, and when closing the user code ClassLoader we null out the reference.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
