Closed
Bug 874956
Opened 12 years ago
Closed 7 years ago
Hook into onXreExit or similar to gracefully end FHR session on Fennec quit
Categories
(Firefox Health Report Graveyard :: Client: Android, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: rnewman, Unassigned)
Details
QuitNow pulls the rug out from under us, finishing the context then killing the process. That's bad for background threads, such as Sync, and it's bad for in-memory state that hasn't been finished and written out (like FHR).
After Bug 868445, any user who uses Quit will have sessions reported as abnormal terminations, because the activity doesn't get a chance to finish... and that's kinda accurate.
We should fix that, ideally by making the termination non-abnormal! We should trim memory and finish our activities, or at the very least politely ask our services and providers to stop.
onTrimMemory == TRIM_MEMORY_UI_HIDDEN would be one way to do this, but it was only added in API 14.
Instead, we'll probably have to modify the quit path to shut down more gracefully.
Comment 1•7 years ago
|
||
Per https://bugzilla.mozilla.org/show_bug.cgi?id=1497137, this component is deprecated. Resolving this bug as incomplete, per :sdaswani.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•