Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upThe onstatus method of webclient causes a memory leak. [SPR-17473] #22005
Comments
This comment has been minimized.
This comment has been minimized.
Rossen Stoyanchev commented Technically, you need to always consume the body of the response, or call In short technically this is not a bug, since the application is generally expected to consume the body. However unlike the case with |
This comment has been minimized.
This comment has been minimized.
KimSeongIl commented Thank you for the reply. there was no memory leak after the code was modified. i expect version 5.1.3 :) |
This comment has been minimized.
This comment has been minimized.
Rossen Stoyanchev commented This should be now fixed if you want to give it a try to 5.1.3 snapshots once the current build completes. |
KimSeongIl opened SPR-17473 and commented
The above source code called an API that responded to 500 errors with 600 tps.
The onstatus method of webclient causes a memory leak.
!스크린샷 2018-11-07 오후 2.01.06.png!
In the photo attached above
We used the onStatus method from 13:40 to 13:48,
We removed the onStatus method from 13:55 to 14:00.
Is this a bug?
Why does the onStatus method cause a memory leak?
I used SpringBoot version 2.0.4 and upgraded to 2.1.0, but I still have a problem.
Affects: 5.0.8, 5.1.2
Attachments:
Issue Links:
Referenced from: commits f73a522, c187cb2
Backported to: 5.0.11