Closed
Bug 1091766
Opened 9 years ago
Closed 9 years ago
Drop messages more gently in ContentChild
Categories
(Core :: DOM: Content Processes, defect)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: mccr8, Assigned: mccr8)
References
Details
(Whiteboard: [MemShrink:P1])
Attachments
(1 file)
924 bytes,
patch
|
bent.mozilla
:
review+
|
Details | Diff | Splinter Review |
Currently, a child process quietly exits when a message to or from it gets dropped. This causes us to not run the rest of shut down, including leak logs. Instead of doing this, I would like to just soldier on. The message is still not going to be sent. Bug 1067633 is on file to track some of the places we send messages too late.
Assignee | ||
Comment 1•9 years ago
|
||
We end up printing a message and failing by returning false higher up in the stack. try runs: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=c123693cd56a https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=4836d88b6fb5
Attachment #8514566 -
Flags: review?(bent.mozilla)
Assignee | ||
Comment 2•9 years ago
|
||
This appears to be causing a failure in B2G ICS Emulator opt M5 in PNeckoChild::SendPCookieServiceConstructor: bool __sendok = (mChannel)->Send(__msg); if ((!(__sendok))) { NS_RUNTIMEABORT("constructor for actor failed"); <-- failure here return nullptr; } I guess before we'd fail to Send(), but just quietly exit(0) there, whereas now we return and NS_RUNTIMEABORT().
Assignee | ||
Updated•9 years ago
|
Attachment #8514566 -
Flags: review?(bent.mozilla)
Assignee | ||
Updated•9 years ago
|
Whiteboard: [MemShrink]
![]() |
||
Updated•9 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P1]
Assignee | ||
Comment 3•9 years ago
|
||
There's a lingering test issue or two, as indicated in the blocking bugs, but I think that's just weird tests, so this seems ready for review. https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=4ac4827a2b0d
Assignee | ||
Updated•9 years ago
|
Attachment #8514566 -
Flags: review?(bent.mozilla)
Comment on attachment 8514566 [details] [diff] [review] Don't exit(0) when a message is dropped in the child process. Review of attachment 8514566 [details] [diff] [review]: ----------------------------------------------------------------- Let's keep a warning at least?
Attachment #8514566 -
Flags: review?(bent.mozilla) → review+
Assignee | ||
Comment 5•9 years ago
|
||
(In reply to ben turner [:bent] (use the needinfo? flag!) from comm
> Let's keep a warning at least?
We actually print out a message higher up the stack, but yeah I can add in something here, in case something else calls into this.
Assignee | ||
Comment 6•9 years ago
|
||
Bug 1103036 seems like a better approach.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 7•9 years ago
|
||
This papers over some shutdown weirdness, even with bug 1103036, so I'm going to go ahead and land it, hopefully today.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee | ||
Comment 8•9 years ago
|
||
e10s try run: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=d6b02c33dce7 full try run: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=7b13debca7e7 Landed with a warning added. https://hg.mozilla.org/integration/mozilla-inbound/rev/e097e82fa29b
https://hg.mozilla.org/mozilla-central/rev/e097e82fa29b
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
You need to log in
before you can comment on or make changes to this bug.
Description
•