-
Notifications
You must be signed in to change notification settings - Fork 38.4k
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
DataBuffer Leak in Server Response #26232
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
Comments
rstoyanchev
added a commit
that referenced
this issue
Dec 7, 2020
rstoyanchev
added a commit
that referenced
this issue
Dec 8, 2020
rstoyanchev
added a commit
that referenced
this issue
Dec 8, 2020
@yinjianfei this should be fixed now in master for 5.3.2 and also backported to 5.2.x and 5.1.x. Those are all expected to release tomorrow. Keep in mind there is also an issue identified in Reactor Core as part of this, see reactor/reactor-core#2534. |
Closed
zx20110729
pushed a commit
to zx20110729/spring-framework
that referenced
this issue
Feb 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
This is based on a report in Reactor Netty reactor/reactor-netty#1408 where the last leak record is in
AbstractJackson2Encoder
with no further records in Reactor Netty, which indicates it gets dropped before it gets there:The scenario is a simple write to the body of a server response:
The use of
WebClient
is probably not key. The main point is that the client (JMeter tests) is set to timeout immediately at 1 ms which sets up a race between writing to the response and the client going away.The full sample https://github.com/yinjianfei/webflux-leak-test.
The text was updated successfully, but these errors were encountered: