If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Lots of "TypeError: can't access dead object" in Browser Console

NEW
Unassigned

Status

()

Firefox
General
2 years ago
2 years ago

People

(Reporter: mconley, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
I've just noticed this recently.

A good chunk of the time, the access is reported to occur at <unknown>, but sometimes I get a stack. Here's one:

16:18:06.682 TypeError: can't access dead object
callListeners() tabbrowser.xml:499
_callProgressListeners() tabbrowser.xml:522
mTabProgressListener/<._callProgressListeners() tabbrowser.xml:571
mTabProgressListener/<.onStatusChange() tabbrowser.xml:831
1 tabbrowser.xml:499:1
(Reporter)

Comment 1

2 years ago
In all likelihood, this is being caused by an add-on. Here's my list of enabled add-ons:

'Sup Son	0.1.1	true	@sup-son
DOM Inspector	2.0.16	true	inspector@mozilla.org
Firefox Hello Beta	0.1	true	loop@mozilla.org
Imgur Uploader	1.0.6.1-signed	true	giorgio@gilestro.tk
Mozilla Tree Status	1.0.1.1-signed	true	mozilla-tree-status@jsantell.com
Pocket	46.0a1	true	firefox@getpocket.com
Restartless Restart	9.1-signed	true	restartless.restart@erikvold.com
Statuser	0.1.0	true	@statuser
tab-crasher	0.1.1-signed	true	jid1-KrxrrWKPOoE4Mw@jetpack
wontfix	1.0	true	jid1-SDCOUnA2RvYHFg@jetpack
You need to log in before you can comment on or make changes to this bug.