ya0yy opened a new issue, #10628: URL: https://github.com/apache/dubbo/issues/10628
<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy --> - [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate. ## Ask your question here java version: 1.8 dubbo version: 2.7.12 I have a dubbo service and it named "main". main service set 500 for provider->threads, so 500 threads to choose from main service when main service called by a dubbo customer.However main service going to call another dubbo service, and it get some results successfully and there results have large size. I look Dubbo put the result to FutureContext(tips: The relevant code is at org.apache.dubbo.rpc.protocol.AbstractInvoker.java:193), but it not be emptied never. This leads that my part of app memory isn't recycled, i.e 500 threads will hold own FutureContext, and every FutureContext will have the large obeject. My app is OOM. <img width="901" alt="image" src="https://user-images.githubusercontent.com/38682203/190363485-dc09e444-feb1-4384-be02-a8c2fce07471.png";> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
![https://user-images.githubusercontent.com/38682203/190363485-dc09e444-feb1-4384-be02-a8c2fce07471.png"](https://user-images.githubusercontent.com/38682203/190363485-dc09e444-feb1-4384-be02-a8c2fce07471.png"){kind=link}