Re:When the memory allocator works against you
by charleslmunger on Sunday March 12, 2017 @02:11PM
(#13852078)
Android handles this by having a total ordering of the importance of every application process, and building its APIs such that process death of something the user isn't interacting with doesn't lose state.
[ Parent
| on HN ]
Re:When the memory allocator works against you
by mikeash on Sunday March 12, 2017 @02:14PM
(#13852098)
iOS is like that too. It keeps all programs running by default, and then when memory gets low it'll start killing them. It starts with backgrounded apps that aren't doing anything, and kills the current foreground app as a last resort.
Apps are supposed to be built to tolerate being killed while in the background and restoring their state when relaunched, so in theory this will mostly be invisible to the user other than apps taking longer to reload. In practice, lots of apps don't get this right.