XN137 commented on issue #1277: URL: https://github.com/apache/curator/issues/1277#issuecomment-4059964978
I just spend quite some time digging through our codebase to find out why a JFR recording showed `Curator-SafeNotifyService-0` threads leaking and double checked we are closing all curator resources ... and only now found this issue 😅 some of our long running integration test modules end up creating 100s of `CuratorFramework` instances in the same JVM. so i am wondering, is there any chance to get a release with this fix? @kezhuw otherwise i might have to provide a custom RunSafeService via the builder and make sure it gets cleaned up on our side. -- 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]
