Closed Bug 750713 Opened 11 years ago Closed 2 years ago

Android Looper on Gecko thread is only processed while Gecko events are also processed

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: snorp, Assigned: snorp)

Details

We have an Android Looper on the Gecko thread, but it is only processed when we have work to do in the normal Gecko loop (see GeckoAppShell::PumpMessageLoop and mozilla::ipc::MessagePump::Run). Looper provides no facility to know when it has work to do, so this is the best we can do right now. The consequence is that Looper tasks are not guaranteed to be run in any reasonable time (or at all).
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.