[ https://issues.apache.org/jira/browse/FLINK-33623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788979#comment-17788979 ]
gabrywu edited comment on FLINK-33623 at 11/23/23 4:52 AM: ----------------------------------------------------------- Flink Netty Client and Fink Netty Server uses different classloader, Netty Server uses sun.misc.Launcher$AppClassLoader, however Flink Netty Client use org.apache.flink.runtime.execution.librarycache.FlinkUserCodeClassLoaders When job stopped, Flink Netty Client thread doesn't stop, so there is always a classloader leak was (Author: gabry.wu): Flink Netty Client and Fink Netty Server uses different classloader, Netty Server uses sun.misc.Launcher$AppClassLoader, however Flink Netty Client use org.apache.flink.runtime.execution.librarycache.FlinkUserCodeClassLoaders > Metaspce leak caused by Flink Netty Client thread > ------------------------------------------------- > > Key: FLINK-33623 > URL: https://issues.apache.org/jira/browse/FLINK-33623 > Project: Flink > Issue Type: Bug > Affects Versions: 1.13.5 > Reporter: gabrywu > Priority: Minor > Attachments: image-2023-11-23-09-47-50-536.png > > > Hi, folks, > We found that there is a Flink Netty Client thread with contextClassLoader > `ChildFirstClassLoader`, and it causes a metaspace leak. > !image-2023-11-23-09-47-50-536.png|width=1175,height=651! -- This message was sent by Atlassian Jira (v8.20.10#820010)