Windows sandbox causes failure of content process output when writing to the console.

RESOLVED DUPLICATE of bug 1247959

Status

()

Core
Security: Process Sandboxing
RESOLVED DUPLICATE of bug 1247959
3 years ago
2 years ago

People

(Reporter: bobowen, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

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

Updated

2 years ago
Duplicate of this bug: 1247959

Comment 2

2 years ago
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.

Updated

2 years ago
Blocks: 1247959
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1247959
You need to log in before you can comment on or make changes to this bug.