Non-Error exception captured with keys: currentTarget, isTrusted, target, type

[SunStupic]

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 Browser CDN bundle

SDK Version

latest

Framework Version

jquery@2.2

Link to Sentry event

https://workstream-is.sentry.io/issues/4086742434/?project=6108198&referrer=jira_integration

SDK Setup

 Sentry.init({
 release: "#{env.SENTRY_RELEASE}",
 });

Steps to Reproduce

No we cannot reproduce it.

Expected Result

No event object should be thrown as error

Actual Result

Weird empty event object is thrown

[SunStupic]

This is similar to the sibling task except

1. it's an exception not an promis rejection
2. The event object is slightly different

Although the doc says I should tell where does this structure come from, but I cannot really tell

{currentTarget: [object Null], isTrusted: True, target: [object Window], type: error}

[Lms24]

Hi @SunStupic thanks for writing in!

Unfortunately, I can't really tell you either where this error is coming from. You mentioned #6199 already and I also think that this is related. Maybe it is also some script that failed to load. Just that it errored instead of throwing a promise rejection. It's very hard for us to diagnose these issues without a reproduction. Happy to look into it if there's a way to reproduce this.

If you you don't want to see this issue, I suggest you use beforeSend to filter it out:

Sentry.init({
 dsn: 'your_dsn',
 // ...
 beforeSend: (event) => {
 const exception = event.exception?.values && event.exception?.values[0]
 if (exception?.value === 'Non-Error exception captured with keys: currentTarget, isTrusted, target, type') {
 return null;
 }
 return event;
 } 
})

[AbhiPrasad]

What's interesting is we've got a spike of these happening as well on the sentry frontend. From looking at Replays with this error, it seems to not impacting the user experience, so it's probably something we can safely ignore.

[harryfear]

This seems to overlap with #2546 ?

We've had a spike in these occurrences also over the last 2 weeks across various web apps, inc. those with no codebase changes whatsoever.

[AbhiPrasad]

Not sure what is going on here, especially since it's happening in all browsers.

Basically this occurs because something is running throw event in an event listener, and because this is not being an error thrown we can't get a stacktrace at all.

Perhaps we should just filter these server side tbh.