You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/02/26 10:16:00 UTC

[jira] [Commented] (FLINK-16245) Use a delegating classloader as the user code classloader to prevent class leaks.

    [ https://issues.apache.org/jira/browse/FLINK-16245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045340#comment-17045340 ] 

Stephan Ewen commented on FLINK-16245:
--------------------------------------

Some thoughts / comments on this are also in https://github.com/apache/flink/pull/11196#issuecomment-591347938

> 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)