Closed Bug 674646 Opened 13 years ago Closed 13 years ago

Do not kill child process when AndroidBridge is not available

Categories

(Core Graveyard :: Widget: Android, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla8

People

(Reporter: alexp, Assigned: alexp)

Details

(Whiteboard: [inbound])

Attachments

(1 file)

Returning false from ContentParent::RecvXXX methods kills the child process. We should return true and handle the error gracefully if it's not really critical.
Methods to be fixed: RecvGetSystemColors, RecvGetIconForExtension.
Is not having the bridge a critical problem?  Sounds like it might be.
Assignee: alexp → nobody
Component: IPC → Widget: Android
QA Contact: ipc → android
(In reply to comment #1)
> Is not having the bridge a critical problem?  Sounds like it might be.

It is, but I don't see how killing the child process helps the situation.
No point in keeping the content process around if we're about to abort.  But you're right, doesn't matter much either way wrt content processes.
(In reply to comment #1)
> Is not having the bridge a critical problem?  Sounds like it might be.

In general it is, but in these two specific cases inability to call those AndroidBridge functions is not really critical. The result would be only cosmetic: some things on the screen might look different, which I believe we can live with if everything else happens to be working.
Assignee: nobody → alexp
Status: NEW → ASSIGNED
Attached patch FixSplinter Review
Attachment #548991 - Flags: review?(blassey.bugs)
Attachment #548991 - Flags: review?(blassey.bugs) → review+
Keywords: checkin-needed
Keywords: checkin-needed
Whiteboard: [inbound]
http://hg.mozilla.org/mozilla-central/rev/33b34c07f8fc
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla8
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: