Without a virtual memory concept it seems, no amount of memory will be able to prevent some one finding some combination of websites that cause a crash.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 7.1's so called Safari fix
- Thread starter GoPro
- Start date
- Sort by reaction score
The thing is, I just use my phone normally. I don't try to find any websites which will crash....and the damn things still crash :-/
I also get FREQUENT page hangs, where a website will start loading and the blue progress bar will get 1/8th of the way across....and just stick there. Only force-closing the app will cure this.
iOS7 is buggy as hell, and also very revealing of a lack of RAM.
I didn't read back but have you tried to restore from new?
I was having similar experiences (maybe not as severe as you) and I did a restore for another problem I was having. Feels like a new phone and is WAY more stable.
Still, given that an average webpage can easily make Retina iPads (the models most prone to crashes because of the highest RAM usage for Web pages) allocate 100-200 MBytes for themselves, adding another 1GB of RAM would seriously reduce the crash / tab reload incidents.
The Android World issue is not a crash, it's a low memory condition where iOS unloads Safari. I can reproduce this easily with that site and can confirm it's a low memory condition as a LowMemory log is generated in Diagnostics & Usage each time I visit the site and rotate several times.have you tried to rotate? and what about http://anonymouse.org/cgi-bin/anon-...le-chromecast-nederland-en-belgie-te-krijgen/ didn't crash?
iOSBry