It's also worth noting that https://searchfox.org/mozilla-central/source/toolkit/components/antitracking/PurgeTrackerService.sys.mjs with high level documentation at https://firefox-source-docs.mozilla.org/toolkit/components/antitracking/anti-tracking/cookie-purging/index.html is probably also important to helping minimize the number of origins. [Searching on the pref](https://searchfox.org/mozilla-central/search?q=privacy.purge_trackers.enabled&path=) it seems like it's enabled, but it would not be surprising if the shorter process lifetimes on Android might cause problems? Specifically, bug 1459974 is absolutely still a thing and I see that the code does use the Storage Activity Service. So there might be an irony that Firefox desktop, which is more able to handle excessive numbers of origins, actually benefits from the purging to have to deal with fewer origins.
Bug 1903530 Comment 26 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It's also worth noting that https://searchfox.org/mozilla-central/source/toolkit/components/antitracking/PurgeTrackerService.sys.mjs with high level documentation at https://firefox-source-docs.mozilla.org/toolkit/components/antitracking/anti-tracking/cookie-purging/index.html is probably also important to helping minimize the number of origins with data stored in QuotaManager. [Searching on the pref](https://searchfox.org/mozilla-central/search?q=privacy.purge_trackers.enabled&path=) it seems like it's enabled, but it would not be surprising if the shorter process lifetimes on Android might cause problems? Specifically, bug 1459974 is absolutely still a thing and I see that the code does use the Storage Activity Service. So there might be an irony that Firefox desktop, which is more able to handle excessive numbers of origins, actually benefits from the purging to have to deal with fewer origins.