Closed Bug 1055731 Opened 10 years ago Closed 7 years ago

[Nuwa] waitpid will always fail

Categories

(Core :: DOM: Content Processes, defect)

Product:
Core
Component:
DOM: Content Processes
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Project Flags:
tracking-b2g backlog

People

(Reporter: khuey, Unassigned)

Details

e.g. http://mxr.mozilla.org/mozilla-central/source/ipc/chromium/src/base/process_util_posix.cc#247

We can't call waitpid anymore post-Nuwa because we will always get ECHILD.  That could cause problems.
[Blocking Requested - why for this release]:
Blocks: CAF-v2.0-CC-metabug
blocking-b2g: --- → 2.0?
I don't think this is fixable for 2.0.  We should block on user-visible symptoms, not engineering issues.
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #2)
> I don't think this is fixable for 2.0.  We should block on user-visible
> symptoms, not engineering issues.

Do you think that it is not related to 3 foreground app seen in bug 1055299 ?
Flags: needinfo?(khuey)
I don't know if it's related or not, but even if it is it's not clear that there's anything usual going on in bug 1055299.
Flags: needinfo?(khuey)
No longer blocks: CAF-v2.0-CC-metabug
No longer a CAF blocker, so moving this to backlog.
blocking-b2g: 2.0? → backlog
Note that waitpid will sometimes fail on direct children as well, thanks to NSPR and bug 227246, so we still need to be able to deal with that case.
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
Nuwa is gone after bug 1284674.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.