Release allocated resources in Zlib, fixes #43. #100
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Together with @KristofferC I managed to find a solution to the memory leak issue (#43). It seems that the allocated resources in zlib are never released, but calling
finalize
does this.It is a bit unclear from the TranscodingStreams documentation whether this is necessary, or if writing the
END_TOKEN
should do this. For example: https://juliaio.github.io/TranscodingStreams.jl/latest/#Wrapped-streams-1 hints that one must do something to release them, but in the code here we don't want to callclose(zWriter)
because that would also close the wrapped stream. https://juliaio.github.io/TranscodingStreams.jl/latest/examples/#Explicitly-finish-transcoding-by-writing-TOKEN_END-1 is a bit unclear what it means to "finishes the current transcoding process without closing the underlying stream", i.e. should that also release the allocated resources or not.Draft for now, since it is possible this is a bug in TranscodingStreams (see JuliaIO/TranscodingStreams.jl#117)