Possible reference leak

Question

Possible reference leak

liuzhengyang opened this issue 8 years ago · comments

LEAK: ByteBuf.release() was not called before it's garbage-collected. Enable advanced leak reporting to find out where the leak occurred. To enable advanced leak reporting, specify the JVM option '-Dio.netty.leakDetection.level:advanced' or call ResourceLeakDetector.setLevel() See http://netty.io/wiki/reference-counted-objects.html for more information.

刘正阳 | bytejava.cn · Answer 1 · Tue Jan 17 2017 19:31:54 GMT+0800 (China Standard Time)

2017-01-17 03:00:16,353 nioEventLoopGroup-5-1 ERROR (ProtocolDecoder:37) - Decoder Result is null this log happend. While this is irrelevant.

刘正阳 | bytejava.cn · Answer 2 · Sat Jan 28 2017 20:05:20 GMT+0800 (China Standard Time)

Haven't happened since that day.