Open
Bug 1400820
Opened 7 years ago
Updated 2 years ago
Window sandboxed child process launch fails with error codes 18 and 0x00000002
Categories
(Core :: Security: Process Sandboxing, defect, P3)
Core
Security: Process Sandboxing
Tracking
()
NEW
People
(Reporter: bobowen, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: sb+)
Found from SANDBOX_FAILED_LAUNCH_KEYED telemetry. Chromium sandbox error code is 18 SBOX_ERROR_CREATE_PROCESS, which can only come from [1]. Windows error is 0x00000002 ERROR_FILE_NOT_FOUND. I can reproduce the same error by renaming firefox.exe and triggering a child launch. So, cause could be manual deletion/renaming or possibly an issue during update. I don't have anything actionable to try and fix this, but we should watch this telemetry as we roll out to see how big the problem is. [1] http://searchfox.org/mozilla-central/source/security/sandbox/chromium/sandbox/win/src/target_process.cc#134
Reporter | ||
Updated•7 years ago
|
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•