Skip to content
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.

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

6.13.2 Introduces Illegal invocation error on global navigator #4006

Closed
2 of 9 tasks
navied opened this issue Sep 23, 2021 · 5 comments · Fixed by #4008
Closed
2 of 9 tasks

6.13.2 Introduces Illegal invocation error on global navigator #4006

navied opened this issue Sep 23, 2021 · 5 comments · Fixed by #4008

Comments

@navied
Copy link

navied commented Sep 23, 2021

Package + Version

  • @sentry/browser
  • @sentry/node
  • raven-js
  • raven-node (raven for node)
  • other: @sentry/react, @sentry/tracing

Version:

6.13.2

Description

It looks like this pr: #3996 might have started couple of issues to show up on sentry see below for screenshot of sentry error:

image

Not sure why it fires, as I haven't been able to reproduce it myself easily.

@AbhiPrasad
Copy link
Member

AbhiPrasad commented Sep 23, 2021

Thanks for raising the issue. This is strange - we guard against this with https://github.com/getsentry/sentry-javascript/blob/master/packages/browser/src/transports/base.ts#L102. We can maybe add an additional check to see if global exists.

Is this a commonly occurring error? How many users are affected by it?

@agrobbin
Copy link

We've had this start happening since 6.13.0 (I think). It's definitely not super-common, but so far we've had 4 errors in the last ~36 hours.

TypeError: Illegal invocation
  at _flushOutcomes(./node_modules/@sentry/browser/esm/transports/base.js:122:22)
  at HTMLDocument.<anonymous>(./node_modules/@sentry/browser/esm/transports/base.js:33:17)

@navied
Copy link
Author

navied commented Sep 23, 2021

After looking into it, it seems like the issue exists in 6.13.1, it just seemed new as I believe we haven't deployed the new 6.13 release yet. It could be based on that, here is a snippet on how many users are effected by it:

image

It tends to happen quite often it seems, but I still cannot reproduce it even while using browser versions mentioned in the events and urls that the users have hit.

@ShannonLCapper
Copy link

Thanks for fixing this! When can we expect #4008 to be deployed to npm?

@kamilogorek
Copy link
Contributor

We'll do it this week

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

Successfully merging a pull request may close this issue.

5 participants