I have an issue with the app. When I return Firefox from the background, the app becomes partially unresponsive: the ui still responds to touches, but the current tab con… (czytaj dalej)
I have an issue with the app. When I return Firefox from the background, the app becomes partially unresponsive: the ui still responds to touches, but the current tab content remains blank for 3–10 seconds. After that delay, the tab content appears and Firefox continues working normally. The issue happens after using other apps for some time before returning to Firefox. It does not happen if I simply switch Firefox to the background and immediately bring it back to the foreground. It looks like a Firefox child/content process may be getting killed or evicted from memory while the app is in the background, but I have modern device with enough free memory (xiaomi 17 ultra, 16 gb ram). I've already tried popular suggestions:
- Disable any restrictions in battery optimizations
- Lock the app in memory
- Allow app autostart
- Disable memory extension (swap) in the system settings
- Checked background process limit - "standard"
The same issue happens on tablet xiaomi pad 6 pro (12 gb of ram, hyperos 3 as x17u). The issue appeared ~4-5 month ago after ordinary Firefox update. What useful logs can I collect to help resolve it?
I've recorded a video of the issue with current versions of Firefox and Firefox Nightly https://youtube.com/shorts/JHxeODD3IQk . On video I reload `example.com` in both browsers, switch to other apps and return back to each browser. Firefox is locked in memory (see icon in task manager), Nightly is not. While tab is stuck in Firefox, I show that UI is working (menu is opened immediately).