Closed
Bug 1122009
Opened 8 years ago
Closed 5 years ago
[e10s] console.group / console.groupEnd in child process corrupts indentation in parent process console e10s
Categories
(DevTools :: Console, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
Attachments
(1 file)
47.94 KB,
image/png
|
Details |
Calling the following from a child process can lead to ever-deeper indenting on the console, see screenshot. This doesn't happen with e10s disabled. console.group() console.group("foo") console.group("bar") console.group("baz") console.groupEnd()
That's supposed to be console.group() console.log("foo") console.log("bar") console.log("baz") console.groupEnd()
tracking-e10s:
--- → ?
Updated•8 years ago
|
Summary: console.group / console.groupEnd in child process does not work properly under e10s → [e10s] console.group / console.groupEnd in child process does not work properly under e10s
To state the problem more precisely: Group logging from the child process corrupts the console in the parent process. - e10s on - open the browser content toolbox - open the browser console - Components.utils.import("resource://gre/modules/devtools/Console.jsm") - repeatedly call this from the child process: console.group() console.log("foo") console.log("bar") console.log("baz") console.groupEnd() - observe parent console getting corrupted Optionally: turn on something in the parent (e.g. gc logging) that causes other log entries to be interleaved with groups from content
Summary: [e10s] console.group / console.groupEnd in child process does not work properly under e10s → [e10s] console.group / console.groupEnd in child process corrupts indentation in parent process console e10s
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•5 years ago
|
Product: Firefox → DevTools
Comment 3•5 years ago
|
||
Seems fine to me now. We still have the thing about logs coming from parent process appearing in groups created by the content page, but there's no much we can do (even UI-wise, that's tricky). The thing that might make that better is Bug 1260877.
You need to log in
before you can comment on or make changes to this bug.
Description
•