iPad Virtual Memory Utility

No, any solution to that would be a jailbreak only. Lack of ram is not the true cause of web browsers crashing on iOS. The Webkit engine has a hard coded limit to the maximum amount of ram used. Once it reaches that limit, it cannot use any more memory even if there is some not being actively used. Most of the crashes are due to bugs within the Webkit engine and the inherit unpredictability of the internet and the webpages contained within it.

 

But if apple had opened up their coin purse, that maximum amount could be larger, and lead to a MUCH better user experience. But in the end, what's more important - claiming the best user experience and maximizing profits. Or actually delivering the best user experience and making a couple less bucks per unit?

 

Because the memory is managed by the OS at the kernel level. Trying to remove that control is in violation of many App Store regulations.

 

Thank god there's some sense in these forums.

 

This doesn't explain why people seem to be getting safari (and system) crashes more often in the latest 2013 devices than they did in last year's devices running iOS 7. Of course, lack of RAM is no explanation either. To my thinking, there's something going on with the A7 and/or 64 bit.

 

Seems Apple can do no wrong in some people's eyes. If the calculator app crashes because someone enters a "D" instead of a number, it is the users fault.

 

Umm, how exactly does one go about entering a D on a numeric keypad?

 

At one time it was possible to copy alpha-text and paste it into Calulator. The result was a crash.

iOS 7's Safari was a large rewrite. Not only for 64-bit, but for iOS 7. Safari is also one of the most complex applications on iOS. Because of this, crashes are more common.