Closed
Bug 1171796
Opened 9 years ago
Closed 9 years ago
[e10s] MOZ_LOG() and stderr from child process are not outputted into log file nor terminal on Windows
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
RESOLVED
FIXED
mozilla42
People
(Reporter: masayuki, Assigned: bobowen)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
I confirmed that only on Windows, MOZ_LOG() doesn't output any logs from child process, although, foo.child-n is created. Additionally, I realized that [Child XXX] isn't printed in my terminal. And also printf() doesn't work too. I'm of course using MozillaBuild. I build debug build and run with: NSPR_LOG_FILE=foo.log NSPR_LOG_MODULES=bar:5 ./mach run -P debug --no-remote Even if I explicitly export the environments before ./mach run, I see same result. I don't see this problem on Linux nor Mac. I hope that this should be fixed ASAP if this bug report is not invalid. Because this blocks supporting TSF in e10s mode.
Reporter | ||
Updated•9 years ago
|
Summary: MOZ_LOG() and stderr from child process are not outputted into log file nor terminal on Windows → [e10s] MOZ_LOG() and stderr from child process are not outputted into log file nor terminal on Windows
Reporter | ||
Updated•9 years ago
|
tracking-e10s:
--- → ?
Reporter | ||
Comment 1•9 years ago
|
||
I realized that when I run mochitest with: ./mach mochitest -f plain <path to a text> Then, I see [Child NNN] lines.
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #2) > Bob, is this caused by the sandbox? Just tested this and yes it is. Looks like we change the env var temporarily in the parent as we launch the child, so if we can get the full path, we should be able to add a rule to the sandbox policy to allow this. Or at worst, just allow *\<log file name>. Masayuki, for the moment you can add an extra environment variable of: MOZ_DISABLE_CONTENT_SANDBOX=1 This will disable the content sandbox and should allow you to get the logging you need. Of course, you will then need to test with the sandbox re-enabled.
Blocks: 1151767
Component: IPC → Security: Process Sandboxing
Flags: needinfo?(bobowen.code)
Hardware: x86_64 → All
Reporter | ||
Comment 4•9 years ago
|
||
> Masayuki, for the moment you can add an extra environment variable of:
> MOZ_DISABLE_CONTENT_SANDBOX=1
>
> This will disable the content sandbox and should allow you to get the logging you need.
> Of course, you will then need to test with the sandbox re-enabled.
Thank you, it's very helpful!
Updated•9 years ago
|
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → bobowen.code
Updated•9 years ago
|
Assignee | ||
Comment 5•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=31496bc64f4e
Assignee | ||
Comment 6•9 years ago
|
||
Bug 1171796: Add sandbox rule for child process NSPR log file on Windows. r?bbondy This also moves the initialization of the sandbox TargetServices to earlier in plugin-container.cpp, because it needs to happen before xul.dll loads.
Attachment #8640492 -
Flags: review?(netzen)
Updated•9 years ago
|
Attachment #8640492 -
Flags: review?(netzen) → review+
Updated•9 years ago
|
Attachment #8640492 -
Flags: review?(netzen) → review+
Assignee | ||
Comment 7•9 years ago
|
||
url: https://hg.mozilla.org/integration/mozilla-inbound/rev/890f4c8154fa21c4ea05cfd6002f67ce7d9d9d7e changeset: 890f4c8154fa21c4ea05cfd6002f67ce7d9d9d7e user: Bob Owen <bobowencode@gmail.com> date: Thu Jul 30 10:04:42 2015 +0100 description: Bug 1171796: Add sandbox rule for child process NSPR log file on Windows. r=bbondy This also moves the initialization of the sandbox TargetServices to earlier in plugin-container.cpp content_process_main, because it needs to happen before xul.dll loads.
Assignee | ||
Comment 8•9 years ago
|
||
That patch addresses the NSPR log file problem. Filed bug 1189223, for the console logging issue.
Status: NEW → ASSIGNED
Comment 9•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/890f4c8154fa
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
You need to log in
before you can comment on or make changes to this bug.
Description
•