[bisq-network/bisq] Fix memory leak caused by not cleaning up unused threads (#3734)

Julian Knutsen notifications at github.com
Tue Dec 3 17:34:36 UTC 2019


What was the memory footprint change after running with your patch? One leaked executor per connection does seem bad, but it would be good to understand the full impact.

Any additional information on which test cases may need to be re-run to verify everything works as expected if this goes into v1.2.4?

Any screenshots or tools we can use to help verify the new behavior?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3734#issuecomment-561275022
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191203/bed9e3b4/attachment.html>


More information about the bisq-github mailing list