Right, now you're merging my answer to two separate problems. I am not the one who doesn't understand the cause.
You said Safari crashed when you hit the button. That is not a "low ram" issue. That is a programming issue, most likely a segmentation fault with the javascript engine - due to poor boundary checking my the developers. You could put 64GB of ram in the thing, that won't stop the issue.
For ****s and giggles, I just tested the memory usage of a UIWebView object loading a basic website (google.com) and the verge (ridiculously over complex). The UIWebView object for google.com used ~4MB of RAM. The one for the Verge used ~14Mb of RAM. Given that tabs are basically wrappers around UIWV with some meta data, you can see the small amounts we are talking here.
Looking at the 5S I'm currently executing on, there's ~650MB available for use right now. That would mean that, if low memory was *really* the problem, I could in theory have >40 verge tabs open before it reloaded, which we know is not the case.
Again, You seem set that "WE NEED MORE MEMORY" is the answer. If you dig into it technically, it's really not.
Crashing due to low memory is in the logs genius. You can read it. Crashing because of not enough memory happens on alot of platforms if you literally don't have enough RAM to load something.
I don't believe you for a second, read this article and go down to where they address 64 bit applications and the memory use on the Air, the iPhone 6 cannot be much different.
http://www.anandtech.com/show/7460/apple-ipad-air-review/9
----------
Well whatever causes this problem Apple have had YEARS to sort it, lol.![]()
It's the RAM, they keep acting like it isn't to justify apples penny pinching in regards to memory. I don't know why they're so quick to go apologist mode whenever this topic is brought up.
Coding isn't magic it can't replace more RAM.