1079275 - Calls to console.log in an actor, with e10s activated, don't produce output in the browser console

Status: RESOLVED DUPLICATE of bug 1067576

(DevTools :: Debugger, defect)

Description

[Patrick Brosset <:pbro>]

In an e10s window, if protocol actors (loaded in the child content process) call 'console.log("test");' or similar, the output goes to the terminal, but not to the browser console.
It would be nice to have it there too.

Comment 1

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Where exactly does the code for the actors live? This may be a dupe of bug 1067576.

Comment 2

[Patrick Brosset <:pbro>]

Actors are loaded in the child process so as to have direct access to the page being debugged.

Comment 3

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Yes, but what matters is the JS scope. Is it in an actual frame script loaded by loadFrameScript, or is the code loaded some other way?

Comment 4

[Patrick Brosset <:pbro>]

I think this is the case. At some stage when the devtools server starts, we load a child frame script:
mm.loadFrameScript("resource://gre/modules/devtools/server/child.js", false);
which, in turn, loads the actors.