Fenix restarts itself soon after getting killed by the user
Categories
(Firefox for Android :: Performance, defect)
Tracking
()
| Performance Impact | low |
People
(Reporter: florian, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf:resource-use)
Attachments
(1 file)
Steps to reproduce
- Start Firefox, browser to any web page
- From the app switcher, kill Firefox
Expected behavior
Firefox no longer running
Actual behavior
Firefox restarts itself soon after getting killed.
Device information
- Firefox version: 124
- Android device model: Pixel 6
- Android OS version: 14
Any additional information?
Here's a profile showing the batterystats and logcat markers: https://share.firefox.dev/43JK0aS
There are a few glean markers that make me wonder if we might be restarting Fenix to send glean pings: https://share.firefox.dev/4amEpcX
If that's the case, we should avoid starting the content and gpu process, and show probably end the main process as soon as the ping has been sent.
Comment 1•1 year ago
|
||
The severity field is not set for this bug.
:kaya, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Reporter | ||
Comment 2•1 year ago
|
||
I saw more evidence of this happening.
More specific steps to reproduce:
- Start Firefox
- Kill it very soon after it started
Often this will cause Firefox to self-restart to send a glean ping (I think this happens if the session was too short for the start of session ping to be sent).
The restart seems to be triggered by the WorkManager component of the operating system. The glean case mentioned above is an easy to reproduce example, but it's just an example, there's other work triggered through WorkManager that can cause restarts too. Markus starting auditing the WorkManager callers we have in our tree.
Here is an example profile from the Gecko Profiler showing what happens within our processes when Firefox gets restarted in the background: https://share.firefox.dev/3R5NO10 (associated logcat & batterystats profile: https://share.firefox.dev/3X2p5yk )
Comment 3•1 year ago
|
||
The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.
Platforms: Android
Resource impact: Some
Comment 4•1 year ago
|
||
Description
•