You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Encountered new issue Permission denied to access object after updating sentry/react #16347
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)
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.
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!
Reacted by Jakob Merrild, Brendan Mulholland and Florian Bienefelt
Activity
bmulholland commentedon May 20, 2025
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 commentedon May 20, 2025
Looks like 9.20.0 is the first broken release for us.
DAcodedBEAT commentedon May 20, 2025
@bmulholland Are you only experiencing this on Firefox too?
yakobe commentedon May 20, 2025
I am also experiencing this. It seems to only affect firefox and is introduced with this change: fcdc4d7#diff-892d9e6e4e05aa1f0080ef9a35343ac223f85e62a0f1aef41af2f03ea8f260eeR3-R454
AbhiPrasad commentedon May 20, 2025
Hey folks - sorry for the trouble here. We're investigating this - appreciate the patience in the meantime.
bmulholland commentedon May 20, 2025
@DAcodedBEAT Actually I only tested this in Firefox...
AbhiPrasad commentedon May 20, 2025
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.
Revert "feat(browser): Track measure detail as span attributes" (#16348)
AbhiPrasad commentedon May 20, 2025
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.AbhiPrasad commentedon May 20, 2025
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.jakobmerrild commentedon May 21, 2025
For what it's worth we only saw this issue for users who had the 1password extension installed when using
sentry/nextjs.AbhiPrasad commentedon May 21, 2025
I see. I guess the
1password extensionemitsperformance.measurewhere 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!
feat(browser): Add detail to measure spans and add regression tests (#…