Skip to content

Errors caused by destroying a stream #143

Description

@matthieusieben

I believe the two following errors are actually caused by the behavior of compress-commons.

It seems that destroying a zip-stream is not 100% supported internally, causing memory leaks and lots of errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions