-
Notifications
You must be signed in to change notification settings - Fork 38.5k
DataBufferUtils.join and Netty Leak LEAK: ByteBuf.release() #34113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
// todo serverRequest.bodyToMono(byte[].class) maybe cause a memory leak when throw DataBufferLimitException 2024-12-18 17:53:18.498 logback [reactor-http-nio-62024-12-18 17:53:18.498 logback [reactor-http-nio-6] ERROR io.netty.util.ResourceLeakDetector - LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information. |
Duplicates #34080 Please don't create duplicate issues. Again, copying many lines of code without minimal sample application won't help here. I wrote a test checking for this and couldn't reproduce the issue you're facing, see https://github.com/bclozel/spring-framework/tree/gh-34113. I'm closing this issue for now until there is a concrete case for us to address. |
Sorry, the first step requires setting the startup parameters: -Dio.netty.leakDetection.level = debug -Dspring.codec.max-in-memory-size = 1 Step 2: Send a request in an endless loop, the length of the request body is greater than 1, and then io.netty.util.ResourceLeakDetector#reportLeak will print the memory leak log、 |
I have shared a unit test that does just that and cannot reproduce the problem. |
thanks you: First of all, you need to make a break point in the following places: |
hello,I now provide a minimal unit of test and it can be reproduced, how can I fix this now。 |
Source code:
The text was updated successfully, but these errors were encountered: