1984783 - Tried to inspect a top menu on a local lichess instance, crashed

Status: RESOLVED DUPLICATE of bug 1979448

(DevTools :: General, defect)

Description

[Nicolas Vaagen]

Error in Web Developer Tools:

Error: Protocol error (NS_ERROR_ILLEGAL_VALUE): Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIXPCComponents_Utils.getSandboxMetadata] from: server0.conn0.watcher3 (resource://devtools/server/connectors/js-process-actor/target-watchers/content_script.sys.mjs:137:0)

Client Packet:

{
  "type": "watchTargets",
  "targetType": "content_script",
  "to": "server0.conn0.watcher3"
}

Server Packet:

{
  "from": "server0.conn0.watcher3",
  "error": "NS_ERROR_ILLEGAL_VALUE",
  "message": "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIXPCComponents_Utils.getSandboxMetadata]",
  "fileName": "resource://devtools/server/connectors/js-process-actor/target-watchers/content_script.sys.mjs",
  "lineNumber": 137,
  "columnNumber": 0
}

Server Stack:

createTargetsForWatcher@resource://devtools/server/connectors/js-process-actor/target-watchers/content_script.sys.mjs:137:25
#watchNewTargetTypeForWatcher@resource://devtools/server/connectors/js-process-actor/DevToolsProcessChild.sys.mjs:203:40
receiveMessage@resource://devtools/server/connectors/js-process-actor/DevToolsProcessChild.sys.mjs:306:50

Stacktrace:

onPacket/<@resource://devtools/shared/protocol/Front.js:404:31
DevTools RDP*request@resource://devtools/shared/protocol/Front.js:320:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:57:19
startListening@resource://devtools/shared/commands/target/target-command.js:532:35

Comment 1

[Julian Descottes [:jdescottes]]

Thanks for reporting the issue. This is probbably a duplicate of Bug 1979448, but even if we landed a fix (in Nightly 144 only at the moment), we don't know the root cause of the issue.

It seems related to webextensions, could you share the information from about:support, especially the list of installed extensions? And can you reproduce this issue consistently? If yes, can you share the steps which trigger the bug? Thanks!

Comment 2

[Julian Descottes [:jdescottes]]

Feel free to reopen if you still experience the issue, but this should have been fixed by bug 1979448.