You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2019. It is now read-only.
When trying to performance test compression part, Hprof dump lists huge number of threads; it looks as if threads were leaked somehow. Since I am closing LzmaOutputStream there seems to be little I can do to prevent this, so it looks like a bug.
(as far as I understand, threads are needed to work around impedance of underlying implementation which does not make it easy to model Java Input/OutputStreams; ideally this shouldn't be needed obviously).
The text was updated successfully, but these errors were encountered:
Test code definitely should have done that, but it has been a while. If that didnt occur, I would consider it a client problem not bug. So as far as I know this is not due to forgetting to close streams.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to performance test compression part, Hprof dump lists huge number of threads; it looks as if threads were leaked somehow. Since I am closing LzmaOutputStream there seems to be little I can do to prevent this, so it looks like a bug.
(as far as I understand, threads are needed to work around impedance of underlying implementation which does not make it easy to model Java Input/OutputStreams; ideally this shouldn't be needed obviously).
The text was updated successfully, but these errors were encountered: