Closed
Bug 1245513
Opened 9 years ago
Closed 9 years ago
Use _exit(0) instead of exit(0) in XPCOM shutdown for content processes on B2G
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla47
Tracking | Status | |
---|---|---|
firefox47 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
Details
Attachments
(1 file)
1.07 KB,
patch
|
mccr8
:
review+
|
Details | Diff | Splinter Review |
In bug 1242119 comment 4, BenWa pointed out that calling exit(0) instead of _exit(0) in content process shutdown in debug builds is likely going to result in some weird behavior. In that bug, I'm removing it entirely on WinXP, but let's change it to _exit(0) on B2G in case that helps.
Assignee | ||
Comment 1•9 years ago
|
||
Carrying over froydnj's r+ from bug 1242119.
Attachment #8715315 -
Flags: review+
Comment 3•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
You need to log in
before you can comment on or make changes to this bug.
Description
•