[ilovejedd]

Originally Posted by tomsem

As the Answer states up front, ‘tl;dr’:

https://stackoverflow.com/questions/...memory-for-ios

That's pretty much the same thing I quoted above. iOS does not have a nonvolatile backing store (e.g. swap or page file on NAND flash) so apps just force quit when it runs out of available RAM.

From the stackoverflow link:

If this was the only way your process is allocating memory, then for most modern operating systems your process would be limited by the amount of unallocated physical memory, plus the amount of free space available in the machine's page file, swap partition, or some other nonvolatile backing store. However, iOS has no backing store and it enforces fairly strict constraints on the maximum resident set size of a process, so generally your app's resident set size will be limited by the lesser of the available physical memory and the per process resident set limit.