Closed Bug 2049094 Opened 4 months ago Closed 4 months ago

[devtools-toolbox-crash] Error: Protocol error (TypeError): can't access dead object from: server0.conn0.watcher2.process72//domwalker24

Categories

(DevTools :: Inspector, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 2042101

People

(Reporter: tdheek, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

If possible, please share specific steps to reproduce the error.
Otherwise add any additional information useful to investigate the issue.

Error in Inspector Panel:

Error: Protocol error (TypeError): can't access dead object from: server0.conn0.watcher2.process72//domwalker24 (resource://devtools/server/actors/inspector/event-collector.js:278:21)

Client Packet:

{
  "type": "querySelector",
  "node": "server0.conn0.watcher2.process72//domnode23",
  "selector": "body",
  "to": "server0.conn0.watcher2.process72//domwalker24"
}

Server Packet:

{
  "from": "server0.conn0.watcher2.process72//domwalker24",
  "error": "TypeError",
  "message": "can't access dead object",
  "fileName": "resource://devtools/server/actors/inspector/event-collector.js",
  "lineNumber": 278,
  "columnNumber": 21
}

Server Stack:

getDOMListeners@resource://devtools/server/actors/inspector/event-collector.js:278:21
getListeners@resource://devtools/server/actors/inspector/event-collector.js:340:28
hasListeners@resource://devtools/server/actors/inspector/event-collector.js:226:17
hasEventListeners@resource://devtools/server/actors/inspector/event-collector.js:807:21
hasEventListeners@resource://devtools/server/actors/inspector/node.js:445:43
form@resource://devtools/server/actors/inspector/node.js:239:37
write@resource://devtools/shared/protocol/types.js:374:32
types.addArrayType/write/<@resource://devtools/shared/protocol/types.js:224:33
write@resource://devtools/shared/protocol/types.js:224:16
write@resource://devtools/shared/protocol/types.js:272:39
write@resource://devtools/shared/protocol/Response.js:101:22
write@resource://devtools/shared/protocol/Response.js:49:28
sendReturn@resource://devtools/shared/protocol/Actor.js:258:38

Stacktrace:

onPacket/<@resource://devtools/shared/protocol/Front.js:405:31
DevTools RDP*request@resource://devtools/shared/protocol/Front.js:321:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:94:19
querySelector@resource://devtools/client/fronts/walker.js:150:34
#getDefaultNodeForSelection/defaultNodeSelectors<@resource://devtools/client/inspector/inspector.js:729:20
#getDefaultNodeForSelection@resource://devtools/client/inspector/inspector.js:736:20

The Bugbug bot thinks this bug should belong to the 'DevTools::Inspector' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Inspector
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Inspector crashes → [devtools-toolbox-crash] Error: Protocol error (TypeError): can't access dead object from: server0.conn0.watcher2.process72//domwalker24

Might be similar to Bug 2042101

By any chance do you have some addons installed? This issue triggers very frequently for me when Stylus is installed.

Flags: needinfo?(tdheek)
See Also: → 2042101
Severity: -- → S3
Priority: -- → P3

(In reply to Julian Descottes [:jdescottes] from comment #2)

Might be similar to Bug 2042101

By any chance do you have some addons installed? This issue triggers very frequently for me when Stylus is installed.

I do have it installed.

Flags: needinfo?(tdheek)

(In reply to Julian Descottes [:jdescottes] from comment #2)

Might be similar to Bug 2042101

By any chance do you have some addons installed? This issue triggers very frequently for me when Stylus is installed.

But it is not the culprit, I think it might be multi account containers.

Thanks for the answer!

It can be another addon, it's not specific to Stylus, even if it is known to trigger the issue.
I'm hopeful this should be fixed by Bug 2042101.

If you still have the issue with Firefox 154, let us know.

Status: NEW → RESOLVED
Closed: 4 months ago
Duplicate of bug: 2042101
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.