I have the same setup with Firefox and Bitwarden without issue. Do you happen to have Firefox setup for restricted battery usage? Android can be quite aggressive with that.
this post was submitted on 30 Aug 2023
54 points (100.0% liked)
Firefox
449 readers
1 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
That, or a phone without much ram. I very often had similar issues on my previous phone when background apps instantly got killed due to memory constrains
Got 6GB and never have issues with other apps. Brave and Chrome are fine.
Thanks, no haven't set up battery restrictions. Have disabled Miui default battery saver, set to no restrictions, still same issue. It happens only when I go to my vault.
Sounds to me it is MIUI that kills a lot of stuff for me all the time, I also don't know how to prevent it.
One way I do is start that other app first, than open needed tab in Firefox and do quick switch between apps. In that way FF is not reloading page, not Bitwarden but might be similar.
It looks like a bug in Firefox, happens on many highend devices as well. https://bugzilla.mozilla.org/show_bug.cgi?id=1807364
Weird. I run the same setup as you (Firefox on Android with Bitwarden and SwiftKey) and I don't think I've ever experienced that. How much RAM does your device have? Do you have a lot of other apps running? It sounds like it is purging the page from memory when you're switching away.
Got 6Gb RAM so should be okay. Also disabled Miui battery saver, no difference. Brave and Chrome work fine.. Strange ay!?
Here is some explanation from firefox dev from two years ago https://www.reddit.com/r/firefox/comments/md63k4/comment/gs8mo2t/
The answer is complicated.
Mobile operating systems don't have swap space. When running multiple apps, a mobile OS needs to be more aggressive at freeing memory than desktop operating systems do. They do this by terminating background processes. The OS uses various heuristics to decide which process(es) to kill.
The problem that you're seeing is not intentional on our part; there isn't something in Firefox that says, "unload everything whenever I go into the background." Instead, it is caused by the content processes being terminated by Android itself.
We know that Chromium-based browsers seem to be working better in this regard. We do not yet have a clear picture about what specifically is causing our content process to be a frequent target.
We're in the process of collecting additional telemetry to help us diagnose this. I've also landed a patch that helps to clean up content process memory usage when Android tells us that it needs memory, in the hope that it will reduce the likelihood of a content process termination. We're also testing Nightly with multiple content processes enabled, which may help.
At any rate, I wouldn't call this problem an intentional design decision, nor would I call it solved. We're doing what we can to learn more about it and get it fixed at some point.
Sounds to me android is by design letting chrome based browsers and killing everything else.
I always use the Bitwarden auto-fill option in my notification shade. You can enable it in the Bitwarden app settings. You can also change how long it takes for the vault to re-lock itself.
Yeah that works, the problem is when I go to my vault, which switches windows. I've extended the timeout so it happens much less. Thanks for the tip.
you could try the Firefox extension version of bitwarden, but it might be annoying to set up. I'm not sure if they approved it in the extension store yet. if not you may have to switch to Firefox nightly or fennec fdroid and then create a custom extension collection. you can look up detailed guides on this.
This is what the latest comment on the git issue says
Using Beta 114, I confirmed that setting dom.ipc.processPrelaunch.lowmem_mb to 0 MB fixes this issue which seems to happen when there's a memory pressure in the system. I can provide a profile with and without this preference if requested. I don't fully understand how this preference affects memory management when dom.ipc.processPrelaunch.enabled is false. Yet somehow it does.
Does this help at all?