Closed Bug 1173698 Opened 4 years ago Closed 4 years ago
Windows sandbox causes failure of content process output when writing to the console
The inheritance of stdout and stderr that was fixed in bug 1009452 only seems to be working when you have stdout/err redirected to a file. It doesn't work when you are just logging to the console. This happens even if security.sandbox.content.level=0, so it shouldn't be a permission issue (unless it is to do with administrator rights). The sandboxing code does launch the process with slightly different settings. For example it uses DETACHED_PROCESS, which might be something to so with this. Non-sandboxed launch starts here: https://hg.mozilla.org/mozilla-central/file/95afddf894e3/ipc/chromium/src/base/process_util_win.cc#l273 Sandboxed launch starts here: https://hg.mozilla.org/mozilla-central/file/95afddf894e3/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp#l36
Here is a good STR for this: 1. run firefox.exe --console 2. open console and type "window.dump('hello!\n');" Observed: the result is not printed in the console window. If one sets the pref browser.tabs.remote.autostart.2=false and restarts the browser to disable e10s, then the STR works.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1247959
You need to log in before you can comment on or make changes to this bug.