[e10s] stderr from sandboxed child process is not output into the terminal on Windows

NEW
Unassigned

Status

()

3 years ago
a year ago

People

(Reporter: bobowen, Unassigned)

Tracking

(Blocks: 2 bugs)

Trunk
All
Windows
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s-, firefox42 affected)

Details

(Whiteboard: sb+)

(Reporter)

Description

3 years ago
+++ This bug was initially created as a clone of Bug #1171796 +++

Follow-up to bug 1171796 for the console logging issue.

Standard logging to the console is not working for the child process with the sandbox turned on.

If you redirect output to a file it does work.
(Reporter)

Comment 1

3 years ago
I think this is a less serious problem than the NSPR logging one as you can work around this by simply redirecting output to a file, which I personally find much more useful anyway.
For example when using mozilla-build:
./mach run &> console.out

However, we should probably track with one of the e10s categories.
tracking-e10s: --- → ?
tracking-e10s: ? → +

Updated

3 years ago
Priority: -- → P1
Whiteboard: sb?
(Reporter)

Comment 2

3 years ago
When the logging tries to do the fprintf we get an ERROR_INVALID_HANDLE.

I'm pretty sure this is the same thing causing the problem in bug 1247959.

Looks like they have same issue with the sandbox on chromium:

https://chromium.googlesource.com/chromium/src/+/79dc59ac7602413181079ecb463873e29a1d7d0a/content/common/sandbox_win.cc#745
See Also: → bug 1247959

Comment 3

3 years ago
known work around using file output.
Whiteboard: sb? → sb+

Updated

3 years ago
Duplicate of this bug: 1247959

Updated

2 years ago
tracking-e10s: + → -

Updated

a year ago
Blocks: 1383253
Priority: P1 → --
You need to log in before you can comment on or make changes to this bug.