Illegal invocation debugging

[pedroabreu]

Hi all,

I've started noticing around the time I've upgraded @sentry/react from 8.47 to 8.48 several Illegal invocation errors in the logs.

There's not much to go for here so a bit stumped on how to even start debugging.

Fullstory does not show any user visible issue.

I'm not sure if this would benefit from enabling tracing in Sentry? Any other ideas on how to even start debugging this?

[lforst]

It's possible that a browser extension or a custom browser is causing this error.

[pedroabreu]

Seems to mostly be on Edge 131/132.

That was my thinking that some weird extension is causing this. Would there be a way to discard these messages or another way to get more information?

[lforst]

If there is a pattern in the errors you can configure the SDK to ignore the errors: https://docs.sentry.io/platforms/javascript/configuration/filtering/

If you want a bit more advanced solution you can try this: https://docs.sentry.io/platforms/javascript/configuration/filtering/#using-thirdpartyerrorfilterintegration

[pedroabreu]

These are the things I can see from the errors:

1. Seems to always be considered a new error. Probably because the hash is always different, e.g. TypeError Illegal invocation ae(iTRKP9te7VhtzjW0kjC3ZhrAtZy4uHxfUHzY8M30-3kx56n-GGa-Rpzmdzn5oXF45X54NBVAG_uxWuFzaucL4Q==)
2. I've merged all events and from the tags and all errors occur on Windows >= 10
3. It seems to be triggered from the DOMContentLoaded event, looking at the arguments section

[{"currentTarget":"[object HTMLDocument]","isTrusted":true,"target":"[object HTMLDocument]","type":"DOMContentLoaded"}]

We are running 8.54.0 react SDK.

Browser usage wise, mostly on Edge

I'm enabling the third party error filtering as you've suggested. If that doesn't work I'mm probably just ignore the error completely.