-
Notifications
You must be signed in to change notification settings - Fork 668
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
report leak when client readtimeout. #1408
Comments
@yinjianfei |
@violetagg thanks for your quick response but unfortunately ,just change 2.1.4.release to 2.4.0 , still exists memory leak.
|
@rstoyanchev Can you take a look at this?
Also from the code above I do not see how this |
@yinjianfei I do not see where in the code you define the read timeout functionality. |
@violetagg |
@violetagg any update from your side? do i need provide more information? |
@yinjianfei I have re-created the issue in the Spring Framework issue tracker where I believe the root cause is. Please subscribe to spring-projects/spring-framework#26232 and give it a try when a fix is available. In the mean time I think this can be closed. |
Thanks @rstoyanchev |
Expected behavior
No leak
Actual behavior
Steps to reproduce
call /leak/test serval times with set client side readtimeout to 1ms.
Reproducable code
logs with setting -Dio.netty.leakDetectionLevel=paranoid, reactor.netty=debug at: https://github.com/yinjianfei/webflux-leak-test/blob/main/console.log
code repo at: https://github.com/yinjianfei/webflux-leak-test
java --version
openjdk version "1.8.0_275"
springboot version
2.1.4.RELEASE
The text was updated successfully, but these errors were encountered: