-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Aborting a CompressionStream/DecompressionStream leaks a resource #14212
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue still exists in Deno v1.23.0. |
I believe this is still a problem. Would it help to give another reproduction scenario? I am seeing it with a |
If inside of a test you call abort() on the writable end of a CompressionStream or DecompressionStream instead of close(), then you get a Deno error about a resource being leaked.
If
sanitizeResources: false
is set, then this gives the expected output:But when run normally, this output happens instead:
The same issue exists with DecompressionStream too.
The same issue also exists if the CompressionStream's readable end is canceled (instead of the writable end being aborted):
Details about error in canceling
Expected output:
Actual output:
The text was updated successfully, but these errors were encountered: