Skip to content

fix: Drop frameless third-party errors from global handler #18342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sentry wants to merge 1 commit into from
+20 −0
Closed

fix: Drop frameless third-party errors from global handler #18342

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions src/instrumentation-client.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,26 @@ Sentry.init({
Sentry.consoleLoggingIntegration(),
],

// Drop frameless errors caught by the global unhandled error handler.
// These are typically from browser extensions or third-party scripts injected
// into the page — they have no stack frames and no app context.
beforeSend(event) {
const framelessUnhandled =
event.exception?.values?.length &&
event.exception.values.every(ex => {
const frames = ex.stacktrace?.frames;
const noFrames = !frames || frames.length === 0;
const mechanism = ex.mechanism;
const isGlobalHandler =
mechanism?.type === 'onerror' || mechanism?.type === 'onunhandledrejection';

@cursor cursor Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong global handler mechanism types

Medium Severity

The new beforeSend filter treats global-handler captures only when mechanism.type is exactly onerror or onunhandledrejection. With @sentry/browser 10.55.0 (this repo’s lockfile), GlobalHandlers sets types like auto.browser.global_handlers.onerror, so isGlobalHandler stays false and frameless extension noise is still sent.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit c46fa04. Configure here.

return noFrames && isGlobalHandler;
});
if (framelessUnhandled) {
return null;
}
return event;
},

// Filter sensitive metric attributes (no PII in metrics)
beforeSendMetric: metric => {
// Remove any accidentally added PII attributes
Expand Down
Loading