Skip to content

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

Closed

Description

@DAcodedBEAT

Is there an existing issue for this?

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)

Activity

  1. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on May 20, 2025
  2. bmulholland commented on May 20, 2025

    @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.

  3. bmulholland commented on May 20, 2025

    @bmulholland

    Looks like 9.20.0 is the first broken release for us.

  4. DAcodedBEAT commented on May 20, 2025

    @DAcodedBEAT
    Author

    @bmulholland Are you only experiencing this on Firefox too?

  5. yakobe commented on May 20, 2025

    @yakobe

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

  6. AbhiPrasad commented on May 20, 2025

    @AbhiPrasad
    Contributor

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

  7. self-assigned this
    on May 20, 2025
  8. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on May 20, 2025
  9. bmulholland commented on May 20, 2025

    @bmulholland

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

  10. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on May 20, 2025
  11. AbhiPrasad commented on May 20, 2025

    @AbhiPrasad
    Contributor

    Does anyone have a reproduction for this? I'm trying to understand why accessing detail (which was the referenced change) can cause issues.

    For now I'm just going to revert this and cut a new release.

  12. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on May 20, 2025
  13. AbhiPrasad commented on May 20, 2025

    @AbhiPrasad
    Contributor

    I published a release request here: getsentry/publish#5589

    After CI passes we'll publish the fix as part of 9.22.0. Thanks again for your patience while we worked on resolving this.

  14. AbhiPrasad commented on May 20, 2025

    @AbhiPrasad
    Contributor

    Hey we've released https://github.com/getsentry/sentry-javascript/releases/tag/9.22.0 with the revert to the feature that introduced this problem in 9.20.0. Please upgrade to resolve this.

  15. jakobmerrild commented on May 21, 2025

    @jakobmerrild

    For what it's worth we only saw this issue for users who had the 1password extension installed when using sentry/nextjs.

  16. AbhiPrasad commented on May 21, 2025

    @AbhiPrasad
    Contributor

    I see. I guess the 1password extension emits performance.measure where they attach a dom element to details that can't get accessed (hence the error gets thrown).

    The wonders of browser library development (but tbh not the worst thing we've seen). Thanks for the info @jakobmerrild!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions