Fix Gecko lifecycle to support multiple activities

NEW
Unassigned

Status

()

Firefox for Android
General
4 years ago
2 years ago

People

(Reporter: liuche, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
ARM
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

"Don't keep activities" causes crashing if we kill Gecko during initialization because we don't handle Gecko teardown if initialization hasn't finished.

This bug is to make lifecycle changes so that we don't get into these undefined states with implicit (limiting) assumptions.
Let's just make sure no existing work is blocked on this bug. Existing work will need to work around the issues. Always be shipping.
Reading Bug 1072831, which spawned this ticket, it becomes clear that it's very difficult to do things that one might naively think are simple, like start Gecko from a lightweight Activity before BrowserApp runs, when BrowserApp owns the Gecko lifecycle.

I think the model this ticket envisions might be a long-lived Android service which encapsulates starting and stopping Gecko (and, presumably, managing the active Gecko profile).  Whee!
See also Bug 964883.
Blocks: 964883
Bug 1074343 is a Fennec system-tray notification that should also be tied to the browser lifecycle.
Blocks: 1074343
You need to log in before you can comment on or make changes to this bug.