Modern MacOS relies heavily on swap. It's not uncommon to see 2-3GB of swap in use at a time, even for a while after memory becomes available. > Some app eatin

Modern MacOS relies heavily on swap. It's not uncommon to see 2-3GB of swap in use at a time, even for a while after memory becomes available. > Some app eating all the RAM? crash right now, please? It's ambiguous which is using "all the RAM." If you have game in one window and browser in another, and you start seeing high memory pressure, which should crash? Or if you're building software and you've fanned out to dozens of processes building dependencies concurrently but all using very little memory independently, which ones should be OOM-killed? Alternatively you can see processes that haven't been woken or taken focus in awhile and page their memory out to swap to release main memory for applications that need it, and avoid crashing or losing data.