Ray7 said:
CyberGeek said:
*snip*


Fairynuff, I just thought it might help you out.

But at the end of the day, none of the problems with the iPhone have been kept a secret. You pays your money and takes your choice.




Quite right that you weren't making guesses, but rather posting guesses from others. I understood the distinction when writing the post, and intended the post as a correction of the often random theories and remedies that arise in forum and comment threads like the ones you linked to, rather than an insinuation that you yourself were coming up with and proposing them, and I apologize that the post came off otherwise.

I read that the guy said that turning on the developer console worked for him. I'm inclined to believe that it hasn't, and that his belief that it has was actually a result of other actions (testing for too short an amount of time, testing on lower-load pages than normal, rebooting the phone relatively shortly before turning on the developer console, or just an outright placebo effect where he's getting crashes just as often but it doesn't feel like it to him).

Yes, there is the very real possibility of specific pages causing crashes due to actual bugs in the browser, and I remember those earlier days of desktop Safari all too well. I do not deny that, but I seriously doubt that asking the browser to display errors that it has already successfully caught would cause it to catch additional errors that it wouldn't have otherwise. I think the probability that the guy didn't conduct a robust test of the reliability of his browser prior to posting is much higher than the probability that turning on the developer console somehow causes the browser to actually successfully catch more errors than when the console is off.

I did read the suggestion about restarting the phone, and I agree with it. My post was an attempt to clarify what is going on internally with Mobile Safari, including stating things that can actually reduce the number of crashes, hence why I restated the restarting suggestion.

Finally, my "criticize away" comment was meant in reference to the iPhone, rather than my post, though it would seem that the post itself ultimately deservedly invited a significant amount of criticism anyway. My post was not intended to be offensive, confrontational, or patronizing, and I apologize if it was any of those things.