-
Bug
-
Resolution: Done
-
Major
-
3.0.10.Final, 3.1.0.CR2
-
None
There is a ByteBuf that is created but never released in ResteasyHttpRequestDecoder. Netty reports this with the following log line:
LEAK: ByteBuf.release() was not called before it's garbage-collected
There is a retain called on the HttpRequest content before the newly created Bytebuf is added to an input stream. I'm not entirely sure why this retain is required so I have attached two different pull requests to this issue. One that drops the retain and one that releases the Bytebuf. I would appreciate any information on why the retain is necessary.
- causes
-
ISPN-6331 Netty buffer leak RESTAsyncIT
- Resolved
-
JDG-708 Netty ByteBuf leak in REST endpoint
- Closed
-
ISPN-6880 Netty ByteBuf leak in REST endpoint
- Closed
- clones
-
RESTEASY-1095 RestEasy-Netty4: ByteBuf leak in ResteasyHttpRequestDecoder
- Closed
- is cloned by
-
RESTEASY-1587 Evaluate different fix for RESTEASY-1205
- Open
- relates to
-
JBEAP-8608 ByteBuf leak in Resteasy 3.0.19.SP1, blocker for JDG
- Closed