alt Hacker NewsStop suggesting this Firefox crap which is not only much slower but it also can't even properly manage RAM usage on mobile, leading to app being killed on my low-RAM device, chrome can deal with it even though that's a "desktop" version with extensions for a much newer high end device.
Restricting webRequestBlocking (but it's not going away, just needs a policy extension) and synchronous executeScript did in practice make adblockers unreliable though.. I partially worked it around by using a custom extension that uses the recent userScripts API..
BTW, it's not possible to inject scripts to workers like a ServiceWorker or to replace it's content (DNR let's you redirect but this redirect breaks SW origin + it's visible when you disallow redirects), but MV2 was no better, chrome extensions never had advanced capabilities for ad blocking, a bug about not being able to access POST data via webRequest was open for 10+ years and will probably never be fixed.
But still, firefox is not the alternative, even WebKit is much better.
Replies
You obviously don't know how Android works. When an app hasn't been open for a while and it has no background tasks, it gets put to sleep. Waking it up takes a second.
You can delay that by selecting the app in the settings and choosing its Battery setting to Unrestricted, however, despite its name, it will still get suspended
The checks are poorly coded. Even on Unrestricted, if you play music from a web player, the browser will get suspended after the song ends but before a new one starts playing because there's a point where it awaits data on the foreground task, Android sees it has no background tasks and suspends it.
How little RAM does your phone have? My Moto G4 Power (less than $200, before the RAM crunch much less) with 2 GB runs Firefox hunky-dory, and I'm one of those triple-digit tab people.