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
Container.followOutput() leaks thread #2276
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case. |
Sorry that we’ve not had a chance to look into this yet. Let’s reopen. |
@rnorth actually, it should be moved to docker-java now :) |
I forgot about this issue, because I had modified our tests to ignore any The good news first: upgrading to testcontainers 1.15.0-rc1 (which includes The bad news is that there is still a thread leak, with a new thread name pattern:
I'm not sure if it's a testcontainers issue or a docker-java issue, but since it's a single thread I'm ok ignoring the new thread name pattern for now. |
@danberindei Thanks for the update! I re-opened the issue so that we remember to investigate Ryuk's leak 👍 |
I am seeing this issue as well |
Container.followOutput()
usesLogUtils.attachConsumer()
, which opens a long-running okhttp request and processes it using aFrameConsumerResultCallback
.The problem is that the
FrameConsumerResultCallback
, so it can't be closed after stopping the container, and the server side doesn't close the connection either, so the processing thread stays alive forever.Our test suite uses an inheritable
ThreadLocal
to track and report thread leaks, and this is what it reports:The text was updated successfully, but these errors were encountered: