Thus disallowing debugging leaks happening in the content processes. Today, switching to the memory panel from the browser content toolbox leads to: TypeError: undefined is not a valid URL.console.error: (new Error("Can't manage front without an actor ID.\nEnsure server supports memory.", "resource://devtools/shared/base-loader.js -> resource://devtools/shared/protocol.js", 1297)) That's mostly because the Content Process actor doesn't export the memory actor: https://searchfox.org/mozilla-central/source/devtools/server/actors/targets/content-process.js#112-113

Seems like a duplicate of the (unassigned) bug 1264873. That other bug may have more information in the comments.

Comment on attachment 8993331 [details] Bug 1476670 - Ensure exposing memory actor for the browser content toolbox. Oh wait I attached it to the wrong bug.