Netty内存泄露

转于自己在公司的Blog：
http://pt.alibaba-inc.com/wp/experience_1348/netty-nio-direct-memory-leak.html

在测试中发现，当不停的开关Netty的NioClientSocketChannelFactory（比如大量连接失败重连等情况下），存在Direct Memory泄露。
测试代码：

for (int i = 0; i < Integer.MAX_VALUE; i ++) {
    ChannelFactory channelFactory = new NioClientSocketChannelFactory(
            Executors.newCachedThreadPool(), Executors.newCachedThreadPool());
    Bootstrap bootstrap = new ClientBootstrap(channelFactory);
    bootstrap.setPipelineFactory(new ChannelPipelineFactory() { ... });
    ChannelFuture future = bootstrap.connect(serverAddress);
    future.await(); // or future.addListener(new ChannelFutureListener() { ... }); 
    Channel channel = future.getChannel();
    channel.close();
    // FIXME NioClientSocketChannelFactory direct buffer memory leak
    channelFactory.releaseExternalResources(); // or bootstrap.releaseExternalResources();
}

抛出的异常信息：

Caused by: java.lang.OutOfMemoryError: Direct buffer memory
at java.nio.Bits.reserveMemory(Bits.java:633)
at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:95)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:288)
at org.jboss.netty.channel.socket.nio.SocketSendBufferPool$Preallocation.<init>(SocketSendBufferPool.java:159)
at org.jboss.netty.channel.socket.nio.SocketSendBufferPool.<init>(SocketSendBufferPool.java:46)
at org.jboss.netty.channel.socket.nio.NioWorker.<init>(NioWorker.java:84)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.<init>(NioClientSocketPipelineSink.java:74)
at org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory.<init>(NioClientSocketChannelFactory.java:135)

询问了Netty的作者Trustin Lee：

Trustin Lee 写道

ChannelFactories are never meant to be created many times. JVM is poor at managing direct buffers, so there's no way to fix this problem without using JNI. One possible workaround would be call System.gc() explicitly, but I'm not sure it's a reliable workaround.

看起来是JVM对direct buffer管理的问题，Netty估计也没有直接的办法解决，
只能静态化ChannelFactory规避，以减少泄露：

private static final NioClientSocketChannelFactory channelFactory = ...;

评论

6 楼 gongjinglin 2016-08-11  

如果new了，服务端没启动的话，会产生大量线程。。。

5 楼 gongjinglin 2016-08-11  

你好，如果重连的话，把NioClientSocketChannelFactory做成静态，不new 一下，会存在问题，一直连接不上报错

Task org.jboss.netty.util.ThreadRenamingRunnable@2c1462a rejected
from java.util.concurrent.ThreadPoolExecutor@e27dc1b[Terminated, pool size = 0,
active threads = 0, queued tasks = 0, completed tasks = 0]

4 楼 guoqingcun 2016-08-02  

牛犇  

3 楼 0dragon 2015-11-27  

本来就是工厂模式  你非要new

2 楼 yanqingluo 2013-04-17  

不太明白.

1 楼 ioly 2012-05-29  

受益！