It's ShockWave that is crashing. It gave errors on FireFox as well, but the difference is that it didn't take the whole program down.
Stella said:The Home of Good Beer![]()
It is shockwave - with firefox it gives an error message like - shockwave performed an illegal operation.... -just update itBornAgainMac said:I reported the link to Apple when prompted after it crashed. I hope the message reaches them rather than just going to /dev/null. Even if it is a Flash issue, Safari should be more graceful in handling the problem.
I hope to see a Phone using OSX technology to compete with phones using Mobile Windows technology. A browser based on Safari technologies is a good step forward along with phones that support H.264 video. My wishlist would be massive support for iSync and iTunes support with cool phones.
ryanw said:I am very confused by this "Mac Mentality". I am an experienced unix engineer who got into mac osx about 2 or 3 years ago. I see this talk of "repair permissions" EVERYWHERE when people talk about problems. What's the big deal about this? Is this "Mac Folklore"?
eSnow said:actually, it is. It does not fix any problem, but people always bring it up as a last resort after they have deleted preferences files.
Superdrive said:Now why is iTunes not on this phone too?
jmufellow said:The exact same thing happened to me! Very ironic. But it is cool that they are embracing safari.
:edit: try this: go to the link provided, then click the link "experience it" on the left. Safari crashes on me everytime... http://www.series60.com/browser
reykjavik said:it crashed my safari....thats irony for ya...
ryanw said:I am very confused by this "Mac Mentality". I am an experienced unix engineer who got into mac osx about 2 or 3 years ago. I see this talk of "repair permissions" EVERYWHERE when people talk about problems. What's the big deal about this? Is this "Mac Folklore"? How is this 'repair permissions' supposed to magically fix random crashes and how things act?? I personally have never done a repair permissions unless I'm on the phone with a mac tech support guy just to get him off my back to say, "Ok, that didn't fix it, now what?".
I see so many people friggin insane about repairing permissions before ANY and ALL updates, and then after every and all updates.
Somebody PLEASE explain where this got started and why this remains to be the remedy that is even leaps and bounds great than Marry Poppins' spoon full of sugar?
ryanw said:I am very confused by this "Mac Mentality". I am an experienced unix engineer who got into mac osx about 2 or 3 years ago. I see this talk of "repair permissions" EVERYWHERE when people talk about problems. What's the big deal about this? Is this "Mac Folklore"? How is this 'repair permissions' supposed to magically fix random crashes and how things act?? I personally have never done a repair permissions unless I'm on the phone with a mac tech support guy just to get him off my back to say, "Ok, that didn't fix it, now what?".
I see so many people friggin insane about repairing permissions before ANY and ALL updates, and then after every and all updates.
Somebody PLEASE explain where this got started and why this remains to be the remedy that is even leaps and bounds great than Marry Poppins' spoon full of sugar?
munkle said:Probably still won't' work with iSync though...![]()
sparkleytone said:If you are a UNIX guy, it shouldn't really be all that foreign to you. For some reason, permissions in OS X have a tendency to get really screwed up. I think it might have to do with (mostly) 3rd party software not cleaning up its own mess, and maybe a bit of leftover garbage from unexpected quits and the like.