Reader was released and can no longer be used to monitor the stream's closedness.

[NikoLandgraf]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/deno

SDK Version

10.47.0

Framework Version

No response

Link to Sentry event

https://fioro-technology-gmbh.sentry.io/issues/110938268/?alert_rule_id=353489&alert_type=issue&notification_uuid=4e18250c-65a3-4ffc-a881-9d99734def99&project=4510546586697808&referrer=slack

Reproduction Example/SDK Setup

// Initialize Sentry for error and performance tracking
Sentry.init({
dsn: Deno.env.get("SENTRY_DSN") || "",
tracesSampleRate: 1.0,
sendDefaultPii: true,
integrations: [Sentry.vercelAIIntegration()],
})

Steps to Reproduce

No Idea

Expected Result

No error

Actual Result

Error inside the sentry package:

ext:deno_web/06_streams.js in readableStreamReaderGenericRelease at line 3004:7
ext:deno_web/06_streams.js in readableStreamDefaultReaderRelease at line 2553:3
ext:deno_web/06_streams.js in ReadableStreamDefaultReader.releaseLock at line 5502:5
/app/node_modules/.deno/@sentry+deno@10.47.0/node_modules/@sentry/deno/build/esm/utils/streaming.js in Object.start at line 90:20
ext:core/01_core.js in eventLoopTick at line 218:9

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear-code]

JS-2107

[andreiborza]

Hi @NikoLandgraf, thanks for filing this.

Looks like we need to handle the rejection from when the lock releases. I'll take a closer look.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #20187, which was included in the 10.49.0 release.