<p>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.</p>
<p>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?</p>
<p>Any screenshots or tools we can use to help verify the new behavior?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/pull/3734?email_source=notifications&email_token=AJFFTNUFRTHBGLQY4BGKZODQW2KCZA5CNFSM4JUXIHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2GBDQ#issuecomment-561275022">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUJFOIVYH6K4IDX4OTQW2KCZANCNFSM4JUXIHYA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNR7GH2T6NQUZ6UYW6DQW2KCZA5CNFSM4JUXIHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2GBDQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/3734?email_source=notifications\u0026email_token=AJFFTNUFRTHBGLQY4BGKZODQW2KCZA5CNFSM4JUXIHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2GBDQ#issuecomment-561275022",
"url": "https://github.com/bisq-network/bisq/pull/3734?email_source=notifications\u0026email_token=AJFFTNUFRTHBGLQY4BGKZODQW2KCZA5CNFSM4JUXIHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2GBDQ#issuecomment-561275022",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>