fix(cloudflare): Consume body of fetch in the Cloudflare transport#18545
Merged
fix(cloudflare): Consume body of fetch in the Cloudflare transport#18545
Conversation
s1gr1d
approved these changes
Dec 19, 2025
This was referenced Jan 9, 2026
12 tasks
Karavil
pushed a commit
to Karavil/sentry-javascript
that referenced
this pull request
Mar 21, 2026
Bun's fetch implementation retains the backing ArrayBuffer of unconsumed response bodies indefinitely. This causes a memory leak when sending many Sentry envelopes, as each response's ArrayBuffer accumulates in memory. This applies the same fix that was made for the Cloudflare transport in getsentry#18545 — consuming the response body with response.text() after extracting the needed headers. In production, this leak manifests as ~8KB ArrayBuffers accumulating at ~8/sec (one per envelope), leading to OOM kills after ~5 hours on containers with 4GB memory limits.
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
2 participants
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.
(closes #18534)
(closes JS-1319)
This consumes the body so it is safe to be closed by Cloudflare Workers. Unfortunately this cannot be reproduced locally and is only happening when the worker is being deployed (so there is no E2E test for this)
@AbhiPrasad do you think it is necessary to add this code snippet in the other transports we have? It is what I've read specifically to Cloudflare, since they seem to be super strict on it, but this could potentially be a problem in other runtimes as well.