Layout debugger dump options don't work with e10s on Windows
Categories
(Core :: Layout, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox127 | --- | affected |
People
(Reporter: JanH, Unassigned)
References
Details
If I run the browser normally from the command line (just call firefox -layoutdebug on a debug build), nothing in the "Dump" menu (except for "Process IDs") works.
Only if I force non-e10s mode via MOZ_FORCE_DISABLE_E10S=1 and MOZ_DISABLE_NONLOCAL_CONNECTIONS=1 do things actually show up in the console window.
Comment 1•1 year ago
|
||
Just to clarify -- when you say they don't work, do you mean the dump has no effect?
On Linux at least, I'm seeing expected results at about:blank and file:// and http://example.org/.
Having said that: if I simply load mozilla.org, I get Assertion failure: false (Receiving unexpected Principal),, which is bug 1758161, which we should ideally fix. (I suspect that's related to cross-origin iframes, or something along those lines.) I wonder if you're hitting a version of that same issue, but it's just manifesting different on your environment?
| Reporter | ||
Comment 2•1 year ago
•
|
||
No, it's not bug 1758161 (though I'm seeing that one, too). I'm simply not seeing anything that's not from the parent process in the console window on Windows. My guess would be some sort of issue with how child process's console/debug output is handled on Windows.
| Reporter | ||
Updated•1 year ago
|
Description
•