fix(http): zstd decoder leaks on capped reads - #783
Open
dwisiswant0 wants to merge 1 commit into
Open
dwisiswant0 wants to merge 1 commit into
dwisiswant0 wants to merge 1 commit into
Conversation
Use synchronous zstd decoding so reaching the body limit does not leave background workers holding decoder buffers. The asynchronous decoder was abandoned without being closed when reading stopped before EOF. Fixes #781 Signed-off-by: Dwi Siswanto <git@dw1.io>
dwisiswant0
force-pushed
the
dwisiswant0/fix/http/zstd-decoder-leaks-on-capped-reads
branch
from
September 16, 2026 20:56
a6e1cf0 to
f134b56
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use synchronous zstd decoding so reaching the body limit does not leave
background workers holding decoder buffers. The asynchronous decoder
was abandoned without being closed when reading stopped before EOF.
Proof
Before:
After (this patch):
For 20 responses expanding from 451 bytes to 4 MiB with a 32 KiB read
limit, leaked goroutines drop from 60 to zero. Retained heap growth
after garbage collection drops from about 111 MB to zero.