There might be a difference in how a browser reacts when a plugin goes amok. At the last WWDC, it was announced that Safari would allow for tabs with plugins that have crashed to be killed without killing the whole Safari app. I don't remember whether that was part of Snow Leopard or Safari 4 in general. I also do not know whether this refers to crashes of plugins or also to plugins that seemingly 'just' use 100% of one core.Indeed it'S a 3rd party addon to the system, but then again how would you explain the vast difference of implementation between Safari and Opera? I bet even the Intel users see a difference there.
Flash is not really a standard, it is a closed proprietary system. In the same way as Windows is not a standard, it might be predominant but it is not a standard.Apple has the alternative for slow @ss Office. And since iWork is around, why should they solve MS Office's problems? Where's the alternative for web's standard flash? Is Apple expecting Silverlight to be the next flash?![]()
I agree its not purple, but I'd say more peachy than tangerine.
i can only hope it solves the crashing issues ive had...![]()
I love Safari except when it comes to PDF files. Then it's an embarrassment.
Apple has the alternative for slow @ss Office. And since iWork is around, why should they solve MS Office's problems? Where's the alternative for web's standard flash? Is Apple expecting Silverlight to be the next flash?![]()
And this is probably a good thing. Snow Leopard doesn't use the same WebKit or the same Safari as Leopard. You wouldn't want to replace them with Leopard versions - you would definitely lose the new features. You might also destabilize the system.Im on snow leopard and when I downloaded it... and tried to install it said I can't because 10.5.8 is required
Could be a mis-calibrated display. I've found that many grays and brushed-metal effects can look purplish if the display isn't calibrated, or if it is calibrated incorrectly.What purple? There's no purple anywhere.
Welcome to the club. I only use Safari as an RSS reader, and even that is getting very aggravating (lots of hangng, resulting in force-quitting.) I've moved to Google Reader for most of my feeds, but GR doesn't support authentication keys/cookies, so I still need Safari for some of the feeds I subscribe to.I'm very close to dropping Safari all together![]()
According to the original article, there should be noting but a few security patches, compared to 4.0.1.I am sure that 4.0.2 has many wonderful improvements but I have seen nothing about SnapBack returning to the address bar.
Have you sent a bug-report to Apple? They might not be aware of this problem.First off I want to thank you for pointing out this problem in a way that actually shows the problem first hand. I showed this to a couple different people who claim that animated gif files have never given them trouble, and it locked them up real quick.
...
This is terrible on Apple's part to have let this problem go on and on like they have.
Have you sent a bug-report to Apple? They might not be aware of this problem.
http://www.apple.com/feedback/macosx.html
Happening to me on almost all sites, including macrumors with Safari 4.02 and a 2009 MP w/ NVidia GT120
i can only hope it solves the crashing issues ive had...![]()
They are... It's fixed in Safari 64-bit in Snow Leopard.
there are some people that think they should be able to swap out spark plugs while the car is still running.
Just change them one at a time.there are some people that think they should be able to swap out spark plugs while the car is still running.
I love Safari except when it comes to PDF files. Then it's an embarrassment.
Warning can cause Safari to crash
Remove the spaces
http://en.wikipedia.org/wiki/ Elastic_collision
If you scroll around the page and then go back up to the top it causes my Safari to 100% and sometimes stops responding.
Could they put back the progress bar please please - who do we have to email - this is silly - why would they do that - it was perfect GUI - perfect mac like. Did anyone complain or maybe it was all those netscape people they hired - not a good thing unless they give them the brain cleanse.
ooooo collisions.
didn't make ff crash, ill try safari
EDIT: hahah safari crashed, have to love command option esc though.
This has been discussed ad nauseam. It's a webkit update and webkit is used throughout the whole OS.
Wow, that stopped Safari responding for a couple of minutes. Surely Apple must know about this?
Tried Safari 4.0.2 on my MBP 15, it's running fine with the URL. No crash. So probably the crashes may be triggered by some incompatible plugins or mismatch configurations?