Post #1736080
2022-11-22 17:17 UTC
@robryk that's a very good question! It provided small benefits compared to this, so we're repurposing it: we want to unload tabs when we're low on physical memory to prevent swapping. This way we'll have two distinct mechanisms, one to prevent crashes and one to improve responsiveness by avoiding swapping.
Replies (1)
-
@robryk@qoto.org 2022-11-22 17:44
@gabrielesvelto Tangentially: I would really appreciate it if Firefox didn't look at how low the _system_ is on memory, but (on OSes where this is a thing) look at the cgroup/other resource allocation process group it's in. (e.g. I run Firefox in a cgroup with a memory limit, so that I can leave some memory aside for everything else in a guaranteed fashion.)