AbstractEpollStreamChannel$EpollStreamUnsafe MemLeak #11761
-
We got the following error message after running our application for some time. Actual behavior
Possible CauseThe byte buffer is set to null on line 796, but it is never released. And in each iteration we create a new byte buffer. Netty version4.1.67 Final JVM version (e.g.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
In the "Possible Cause" snippet, the |
Beta Was this translation helpful? Give feedback.
-
Converting to GH discussion |
Beta Was this translation helpful? Give feedback.
-
I face the same issue - byteBuf is set to null but still has a reference count > 0 after the call to Netty version is 4.1.68.Final |
Beta Was this translation helpful? Give feedback.
-
@pravussum the handler in the |
Beta Was this translation helpful? Give feedback.
-
We will check our InputHandlers if one of them does not release the buffer correctly. |
Beta Was this translation helpful? Give feedback.
@pravussum the handler in the
ChannelPipeline
that "consumes" the buffer is responsible to callrelease()