Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

notmenwohere

macrumors member
Original poster
Nov 1, 2013
69
0
Guys,

Is there an app to do a swap file (storage to ram)?

Preferably non-jb app.

This will most likely solve the Safari and Chrome crashing issue. I hope at least.
 
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?
 
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.

So this means that an software update could potentially solve the problem. Butnstill, why doesn't Apple allow dev teams to develope ome swap file app. I mean apple did copied some jb app such as sbsetting.
 
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.
 
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.

Thank god there's some sense in these forums.
 
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.

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?
 
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.

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.

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.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.