Actually, it is probably being force-closed by iOS due to low memory (check the logs), which isn't really the same as crashing due to iOS bugs (i.e., it is intentional behavior). It is likely designed to deter a single [badly coded/overly complex/poorly optimized] web page (or app, really) from trying to use more RAM than the phone has. The idea is "why would you want to keep something loaded that is barely usable in the first place?"
But you are right, browser crashes are not okay.
Disclaimer: I'm inferring much of this and simplifying somewhat.
Because it is CRAP website...![]()
Sometimes your data gets screwed up, sometimes you hit a page that is implemented so poorly that your browser crashes. You can't expect software to be able to handle every single edge case and random error.
I'm pretty sure the person you quoted said iOS 7. They made no mention of the beta. What's the excuse for iOS 7 being so buggy?
Has the volume or ringer image that shows on the screen gone when your adjusting the volume while watching something?
I've done a LOT of work with UIWebView - the core component of Safari. I've talked a lot with the dev of iCab Mobile, Alexander Clauss, on these matters. So I do know what I'm speaking about:
It's mostly because of the enormous RAM memory usage of that widget that crashes (and, in Safari, killed tabs) are abound, not those of Web pages. Surely, some Web pages can crash Safari even with plenty of RAM available (this is how the 4.3 JB became possible), but you need to search very hard to find such pages. Casual pages don't crash Safari.
Let me, as a programmer who played with RAM allocation back in even the iPhone 3G times when every single byte counted, chime in.
There is absolutely no memory protection in iOS. This means if you allocate a given size of RAM, and there is not so much free RAM available, your app will crash. This is why many apps crash now and then when run without manually killing all previous apps / resetting first.
This is REALLY a PITA as
- malloc()'s simply failing (signalling it didn't allocate the asked-for RAM) would be preferred to (the current) crashing for obvious results (much better for end users; you can gracefully exit or, say, opt for displaying "Not enough RAM, kill bg tasks / reset" messages.)
- UIWebView behaves exactly the same way: if you load a page that simply doesn't fit in the memory when decoded, your app will crash. And, as I've pointed out above, UIWebView uses TONS of memory - sometimes even hundreds of megabytes for a larger Web page on a Retina iPad.
RAM memory
seriously...boo hoo ? that's the level we're working on ....whatever, the lockout process is poorly implemented.
Well excuse me Mr. I Am A Developer - some of us would like our phones to be actually functioning properly without bugs and crashes left and right.
The only reason I want to upgrade is due to the fact that iOS 7.0.3 and 7.0.4 have been complete ***** for me in regards to usability.
Phone calls do not come in and the only way I know I had a phone call is because a few minutes later I get a VM indicating so.
On top of that iOS 7 is so buggy that I have to constantly press my home button before it actually even does anything. No my home button isn't defective nor is it broken, it worked fine all day every day while I was on iOS 6.
1. New zoom animation on wallpaper when waking the phone from sleep.
How original. You're like an Apple devoted version of Carlos Mencia.
Not sure if you were sarcastic, but Apple usually doesn't put anything related to user facing features in beta release notes unless it can affect developers.
This is also true for bug fixes in the user interface or built-in apps, some fixes might not be listed in the release notes.
Yes! Love that! Same on the lock screen?
Just to be clear. You can tap the are where the song and album title are now and it'll take you to the music app as well. This isn't new in 7.1.
(Though who would know given that text and buttons look the same now...)
I think that may be a bug?
Might be good to actually read the available information and see that there are quite a few more changes beyond some little things like Yahoo! logo changes (they they probably just had to do and call out contractually).Have to say that every time i read this updates I simply laugh...
This are the big changes?
Changing yahoo icon?
Are you kidding me apple?
What is going on there, the base at cupriteno are simply disconnected from the tech market.
This year unless apple will introduce something very diffrent in ios 8, it is the end of this os.
And the final winning of the android.