LEAK: ByteBuf.release() error #3376
Comments
|
Have you tried with the latest 2023.0.1? There have been a number of fixes in this area. |
|
We have not upgrade beyond the current versions as we are blocked from doing so until we rewrite the logic that uses the WebFluxTags |
|
Let me know when you get a chance. |
|
Thank you Spencer Gibb we have prioritized that work and should be able to update soon if there are still any issues remaining. |
spencergibb
added
feedback-provided
waiting for feedback
and removed
waiting for feedback
feedback-provided
labels
|
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
|
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have been experiencing issues with the "LEAK: ByteBuf.release()" error. We have been addressing our shortcomings in
an effort to eliminate them and while we have seen improvements we are still having an issue for which we believe
is happening in the spring library.
We feel a lot of the issues we saw happened in the code where we used the ModifyRequestBodyGatewayFilterFactory or
ModifyResponseBodyGatewayFilterFactory and a publisher to make changes to the request or response. In same cases we would
pass through this logic needlessly. We have reduced the flow to just changes in the exchange for the request with a final
filter that uses the ModifyRequestBodyGatewayFilterFactory and publisher to handle the rewrite however it appears from
the logging we are still seeing memory leaks around this logic.
Most of the stack traces we are now seeing all appear to start with the same 8 lines like the following.
A stack trace of a specific example of the issue follows:
This is a portion of the logging related to the trace id on the above stack trace and is limited to the
ModifyRequestBodyFromExchangeFilter and "LEAK: ByteBuf.release()" error that is happening in the middle of the filter
indicating to us that it seems to be happening while the spring code is running which is consistent with those first
8 lines of the stack trace.
This is the filter is, the debug logging was added when we started to observe memory leaks after the rewrite.
Java version: 17
Spring boot version: 3.1.9
Spring cloud version: 2022.0.5
JVM args passed:
-XX:MaxRAMPercentage=80.0
-Dio.netty.leakDetection.level=PARANOID
The text was updated successfully, but these errors were encountered: