Telemetry probe to measure the number of times we get killed in the background
Categories
(Firefox for Android :: Browser Engine, task)
Tracking
()
People
(Reporter: csadilek, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid])
From github: https://github.com/mozilla-mobile/android-components/issues/9999.
Individual issue to track new telemetry related to page persistence metrics.
- number of times we get killed in the background using
onKill (for content process) and
getHistoricalProcessExitReasons for main process https://developer.android.com/reference/kotlin/android/app/ActivityManager#gethistoricalprocessexitreasons (API30 only I think)
This metrics could help us track how memory/performance affects retaining tabs/getting killed and how often our users get their tabs reloaded. Also it can help us know how many tabs are actually alive in users devices (e.g. when thinking about memory/performance tradeoffs based on number of tabs)
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Updated•3 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
•
|
||
As mentioned in the github comment, this task would be to measure number of times background tabs get killed and their corresponding getHistoricalProcessExitReasons
. onKill
is already tracked by https://github.com/mozilla-mobile/fenix/pull/17864.
Updated•2 years ago
|
Comment 2•1 year ago
|
||
Clearing Priority so we can reprioritize these bugs relative to our ux-fun-2024 bugs.
Updated•2 months ago
|
Description
•