我创建了一个小型Netty服务器来计算BigInteger的阶乘并发送结果。代码如下。
阶乘
public class Factorial {
private int port;
public Factorial(int port) {
this.port = port;
}
public void run(int threadcount) throws Exception {
EventLoopGroup bossGroup = new NioEventLoopGroup();
EventLoopGroup workerGroup = new NioEventLoopGroup(threadcount);
try {
ServerBootstrap b = new ServerBootstrap();
b.group(bossGroup, workerGroup)
.channel(NioServerSocketChannel.class)
.childHandler(new ChannelInitializer<SocketChannel>() {
@Override
public void initChannel(SocketChannel ch) throws Exception {
ch.pipeline().addLast(new FactorialHandler());
}
})
.option(ChannelOption.SO_BACKLOG, 128)
.childOption(ChannelOption.SO_KEEPALIVE, true);
ChannelFuture f = b.bind(port).sync();
f.channel().closeFuture().sync();
} finally {
workerGroup.shutdownGracefully();
bossGroup.shutdownGracefully();
}
}
public static void main(String[] args) throws Exception {
int port = 15000;
new Factorial(port).run(Integer.parseInt(args[0]));
}
}
FactorialHandler.java
public class FactorialHandler extends ChannelInboundHandlerAdapter {
@Override
public void channelRead(ChannelHandlerContext ctx, Object msg) {
BigInteger result = BigInteger.ONE;
String resultString;
for (int i=2000; i>0; i--)
result = result.multiply(BigInteger.valueOf(i));
resultString = result.toString().substring(0, 3)+"\n";
ByteBuf buf = Unpooled.copiedBuffer(resultString.getBytes());
ctx.write(buf);
ctx.flush();
}
@Override
public void exceptionCaught(ChannelHandlerContext ctx, Throwable cause) {
cause.printStackTrace();
ctx.close();
}
}
当我运行此程序时,出现以下错误
Jun 08, 2018 5:28:09 PM io.netty.util.ResourceLeakDetector reportTracedLeak
SEVERE: LEAK: ByteBuf.release() was not called before it's garbage-collected. See http://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
如给定链接中所述,我通过在
buf.release()
之后在channelRead方法中调用ctx.flush()
来释放ByteBuffer。但是当我这样做时,服务器开始引发以下异常
io.netty.util.IllegalReferenceCountException: refCnt: 0, increment: 1
有人可以告诉我如何解决此问题吗?
最佳答案
问题不在于出站ByteBuf。出站ByteBuf总是为您服务(请参见OutboundMessages)。问题是入站ByteBuf。我在看着你,FactorialHandler。它扩展了ChannelInboundHandlerAdapter。请从JavaDoc注意:
请注意,在
channelRead(ChannelHandlerContext,Object)方法返回
自动。如果您正在寻找ChannelInboundHandler
自动释放接收到的消息的实现,
请参阅SimpleChannelInboundHandler。
您的处理程序具有如下签名:
public void channelRead(ChannelHandlerContext ctx, Object msg)
该msg(顺便说一句您不使用)实际上是一个ByteBuf,这正是上述JavaDoc所警告的内容。 (在没有其他ChannelHandler的情况下,消息将始终是ByteBuf的实例。)
因此,您的选择是:
使用SimpleChannelInboundHandler将为您清理该引用。
在处理程序的末尾,使用ReferenceCountUtil.release(java.lang.Object msg)释放入站ByteBuf。
关于java - 由于Netty中的ByteBuffers而导致的内存泄漏,我们在Stack Overflow上找到一个类似的问题:https://stackoverflow.com/questions/50760506/