Encountered new issue `Permission denied to access object` after updating sentry/react

[DAcodedBEAT]

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/react

SDK Version

9.21.0

Framework Version

React 19.1.0

Link to Sentry event

https://cork-protection-inc.sentry.io/issues/6618656269?project=4505727305646080

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. updated sentry dependencies
2. errors came in

Expected Result

1. update sentry dependencies
2. no errors should be caused by sentry

Actual Result

Error: Permission denied to access object
  at _addMeasureSpans(../../node_modules/@sentry-internal/browser-utils/build/esm/metrics/browserMetrics.js:255:41)
  at X2e/<(../../node_modules/@sentry-internal/browser-utils/build/esm/metrics/browserMetrics.js:194:9)
  at addPerformanceEntries(../../node_modules/@sentry-internal/browser-utils/build/esm/metrics/browserMetrics.js:174:48)
  at idleSpan.beforeSpanEnd(../../node_modules/@sentry/browser/build/npm/esm/tracing/browserTracingIntegration.js:90:9)
  at span.endapply(../../node_modules/@sentry/browser/node_modules/@sentry/core/build/esm/tracing/idleSpan.js:52:9)
  at Coe/<(../../node_modules/@sentry/browser/node_modules/@sentry/core/build/esm/tracing/idleSpan.js:196:12)
  at sentryWrapped(../../node_modules/@sentry/browser/build/npm/esm/helpers.js:38:17)

[bmulholland]

Uh yeah, we just had this cause a production incident. Made our entire app unresponsive. Vue instead of React, though. Our tests didn't catch it because Sentry isn't enabled for automated tests.

[bmulholland]

Looks like 9.20.0 is the first broken release for us.

[DAcodedBEAT]

@bmulholland Are you only experiencing this on Firefox too?

[yakobe]

I am also experiencing this. It seems to only affect firefox and is introduced with this change: fcdc4d7#diff-892d9e6e4e05aa1f0080ef9a35343ac223f85e62a0f1aef41af2f03ea8f260eeR3-R454

[AbhiPrasad]

Hey folks - sorry for the trouble here. We're investigating this - appreciate the patience in the meantime.

[bmulholland]

@DAcodedBEAT Actually I only tested this in Firefox...