can't access dead object

[jordyvandomselaar]

Our Bugsnag is reporting the following error:

TypeError can't access dead object 
    ../node_modules/@bugsnag/browser/dist/bugsnag.js:2262 init/t.onreadystatechange

Unfortunately that's all we have, it's the full stacktrace which led me to believe it's an issue with this package.

Currently I don't know of any way to reproduce this so I can't cook up an example.

Is this a known issue?

[mattdyoung]

Hi @jordyvandomselaar

That error is explained in more detail here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Dead_object

Is your project a browser extension?

[jordyvandomselaar]

Hey @mattdyoung,

Thanks for replying! It's not a browser extension =), it's a react app running in the browser

[mattdyoung]

Hi @jordyvandomselaar

Actually, we think this could happen just due to an extension installed on the web browser where the code was run.

Is this something you've seen yourself when testing or only from one of your users? Are you able to find out about any installed browser extensions?

It would be good to find a way to reproduce to confirm the root cause.

[jordyvandomselaar]

Hi @mattdyoung ,

Actually, we think this could happen just due to an extension installed on the web browser where the code was run.

We came to the same conclusion initially but because the stacktrace only showed Bugsnag we figured it could also have to do with Bugsnag =)

Is this something you've seen yourself when testing or only from one of your users? Are you able to find out about any installed browser extensions?

I am unable to reproduce this myself, Bugsnag has been reporting this error a number of times and we're investigating what might be the cause.

Unfortunately, I am unable to see what extensions our users have installed

[mattdyoung]

Hi @jordyvandomselaar

We've seen some other instances of this error now but the line of code and stacktrace reported appears to differ although all occurrences are in Firefox browsers.

We're fairly confident this is due to a misbehaving Firefox add-on. We'd like to try and reproduce to be sure, but are also struggling to find a way to reproduce or find an occurrence from someone where we know which addons are installed.

If you find any way to reproduce please let us know, and similarly we'll report back here if we find more info.

[jordyvandomselaar]

Hi @mattdyoung,

You're the best!

I can confirm that it has only been happening with Firefox users and I'll keep trying to find reproduction steps.

Thanks for thinking with me and I'll keep you posted if something pops up! =)