Only if you're confusing "crash" with "terminated by iOS". Yes, a crashlog will be generated, but technically that's iOS doing what it's designed to do in killing the foreground app after (1) asking all apps to free up memory, then (2) terminating every other background app in an effort to free up memory before finally (3) terminating the foreground app. For a
web browser to do that when no other apps seem to suffer the same trouble just doesn't make sense. Why wouldn't we see the problem even worse with some of the multi-GB games?
Correct that iOS doesn't have a swap file. That's why it has a different memory management style than a paging OS.
See
https://developer.apple.com/library...tual/ManagingMemory/Articles/AboutMemory.html and
https://developer.apple.com/library/ios/technotes/tn2151/_index.html
I have a handful of low memory logs on my rMini. Oddly only Safari seems to create them when other memory hungry apps have no issues. Same on my iphone5s; five low memory logs, seven Safari.
Even stranger, all but a couple show thousands of free pages and even a couple of them (rMini) show Free Pages of 29730 and 23703. At 4kb a page, that's 93MB and 116MB of free memory at the time of a LowMemory crashlog.
Also odd is the lack of complaints of Safari low memory crashes on mini1s and ipad2s. Shouldn't the situation be even worse? Even if apps truly use a full 30% more RAM on the 64bit platform (I'm not convinced the reality is that large a figure), we should still see more low memory issues on the 32 bit platform when there's half as much memory.
Certainly there's something going on, but I'm just not seeing the evidence to support any conclusion as to the root cause.