-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
CoExchangeFilterFunction introduces potential memory leak if coroutine is cancelled #34210
Comments
Based on my observation, it looks like this error is triggered by the second delay that simulates the response post-processing. Also the memory leak seems to be a side effect triggered by a previous error:
@mlukasanderson Can you confirm this is also what you see? @violetagg Any thought of the potential cause? |
This seems similar to reactor/reactor-netty#3591 |
@violetagg Thanks, I will test with snapshots. |
Good catch @violetagg, I confirm Reactor Netty |
We are seeing leak logs similar to the below on a regular basis in a production application which uses a number of WebClient filters implemented with CoExchangeFilterFunction. Appears that a leak can occur if coroutine is cancelled in the filter function.
Example application reproducing the issue can be found here.
Example output:
The text was updated successfully, but these errors were encountered: