即使發佈之後Netty資源泄漏

爲什麼以下內容被視爲泄漏？即使發佈之後Netty資源泄漏

2016-12-04 09:24:01,534 ERROR [epollEventLoopGroup-2-1] [io.netty.util.ResourceLeakDetector] - 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: 5 
#5: 
     io.netty.buffer.AdvancedLeakAwareByteBuf.release(AdvancedLeakAwareByteBuf.java:955) 
     com.example.network.listener.netty.PreprocessHandler.handle(PreprocessHandler.java:42) 
     com.example.network.listener.netty.UdpHandlerChain.handle(UdpHandlerChain.java:17) 
     com.example.network.listener.netty.UdpRequestExecutor$1.run(UdpRequestExecutor.java:89) 
     java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
     java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
     java.lang.Thread.run(Thread.java:745) 
#4: 
     io.netty.buffer.AdvancedLeakAwareByteBuf.readBytes(AdvancedLeakAwareByteBuf.java:495) 
     com.example.network.listener.netty.PreprocessHandler.handle(PreprocessHandler.java:39) 
     com.example.network.listener.netty.UdpHandlerChain.handle(UdpHandlerChain.java:17) 
     com.example.network.listener.netty.UdpRequestExecutor$1.run(UdpRequestExecutor.java:89) 
     java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
     java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
     java.lang.Thread.run(Thread.java:745) 
#3: 
     io.netty.buffer.AdvancedLeakAwareByteBuf.retain(AdvancedLeakAwareByteBuf.java:927) 
     io.netty.buffer.AdvancedLeakAwareByteBuf.retain(AdvancedLeakAwareByteBuf.java:35) 
     io.netty.util.ReferenceCountUtil.retain(ReferenceCountUtil.java:36) 
     io.netty.channel.DefaultAddressedEnvelope.retain(DefaultAddressedEnvelope.java:89) 
     io.netty.channel.socket.DatagramPacket.retain(DatagramPacket.java:67) 
     io.netty.channel.socket.DatagramPacket.retain(DatagramPacket.java:27) 
     io.netty.util.ReferenceCountUtil.retain(ReferenceCountUtil.java:36) 
     com.example.network.listener.netty.UdpRequestExecutor.channelRead(UdpRequestExecutor.java:71) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) 
     io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) 
     io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) 
     io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) 
     io.netty.channel.epoll.EpollDatagramChannel$EpollDatagramChannelUnsafe.epollInReady(EpollDatagramChannel.java:580) 
     io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:402) 
     io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:307) 
     io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) 
     io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) 
     java.lang.Thread.run(Thread.java:745) 
#2: 
     Hint: 'UdpRequestExecutor#0' will handle the message from this point. 
     io.netty.channel.DefaultAddressedEnvelope.touch(DefaultAddressedEnvelope.java:117) 
     io.netty.channel.socket.DatagramPacket.touch(DatagramPacket.java:85) 
     io.netty.channel.socket.DatagramPacket.touch(DatagramPacket.java:27) 
     io.netty.channel.DefaultChannelPipeline.touch(DefaultChannelPipeline.java:107) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356) 
     io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) 
     io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) 
     io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) 
     io.netty.channel.epoll.EpollDatagramChannel$EpollDatagramChannelUnsafe.epollInReady(EpollDatagramChannel.java:580) 
     io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:402) 
     io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:307) 
     io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) 
     io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) 
     java.lang.Thread.run(Thread.java:745) 
#1: 
     Hint: 'DefaultChannelPipeline$HeadContext#0' will handle the message from this point. 
     io.netty.channel.DefaultAddressedEnvelope.touch(DefaultAddressedEnvelope.java:117) 
     io.netty.channel.socket.DatagramPacket.touch(DatagramPacket.java:85) 
     io.netty.channel.socket.DatagramPacket.touch(DatagramPacket.java:27) 
     io.netty.channel.DefaultChannelPipeline.touch(DefaultChannelPipeline.java:107) 
     io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356) 
     io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) 
     io.netty.channel.epoll.EpollDatagramChannel$EpollDatagramChannelUnsafe.epollInReady(EpollDatagramChannel.java:580) 
     io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:402) 
     io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:307) 
     io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) 
     io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) 
     java.lang.Thread.run(Thread.java:745) 
Created at: 
     io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:271) 
     io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:179) 
     io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:170) 
     io.netty.buffer.AbstractByteBufAllocator.ioBuffer(AbstractByteBufAllocator.java:131) 
     io.netty.channel.DefaultMaxMessagesRecvByteBufAllocator$MaxMessageHandle.allocate(DefaultMaxMessagesRecvByteBufAllocator.java:73) 
     io.netty.channel.RecvByteBufAllocator$DelegatingHandle.allocate(RecvByteBufAllocator.java:124) 
     io.netty.channel.epoll.EpollDatagramChannel$EpollDatagramChannelUnsafe.epollInReady(EpollDatagramChannel.java:544) 
     io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:402) 
     io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:307) 
     io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) 
     io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) 
     java.lang.Thread.run(Thread.java:745)

上次訪問是一個明確的release() ......

我使用了Netty 4.1.6.Final。

來源

2016-12-04 Mickael Marrache

異常消息指向Netty Wiki。從這些信息和痕跡看起來像在com.example.network.listener.netty.UdpRequestExecutor.channelRead(UdpRequestExecutor.java:71)是錯誤的。無論如何，在你的緩衝區引用的時候是> 0。你應該研究例子和責任矩陣來正確使用refcounts。

來源

2016-12-05 18:14:18 IrLED

請注意，此錯誤在我的日誌中只出現一次......它怎麼可能？服務器收到大量的請求.... –

我不知道你配置泄漏檢測的方式。默認情況下，它採樣〜1％的緩衝區。無論如何，對於特定的buf（來自日誌），很明顯爲什麼它被認爲是泄漏 - 過度使用'retain（）' – IrLED

這讓我困惑......我在尋找一個緩衝區泄漏......所有緩衝區都被泄露。謝謝 –

即使發佈之後Netty資源泄漏

回答

相關問題