Save Mr. Crashy Pants January 6, 2008 6:26 AM Subscribe
Add as a contact may or may not be broken, but it crashes Safari.
Logging in again using Firefox, I verified that the contact I wanted to add was added, but that was after Safari crashed on me. I pressed the "Add" button in Safari, it hung for a few seconds and then quit. (Safari 3, Mac OS X 10.4.11) Not a huge issue since adding the contact actually worked, but I had other tabs open in Safari that I needed to go back and open again.
Logging in again using Firefox, I verified that the contact I wanted to add was added, but that was after Safari crashed on me. I pressed the "Add" button in Safari, it hung for a few seconds and then quit. (Safari 3, Mac OS X 10.4.11) Not a huge issue since adding the contact actually worked, but I had other tabs open in Safari that I needed to go back and open again.
I just added you as a contact and it worked fine. Same specs.
posted by dobbs at 7:43 AM on January 6, 2008
posted by dobbs at 7:43 AM on January 6, 2008
I added dobbs as a contact. Same specs here, too, and worked fine.
posted by cgc373 at 8:14 AM on January 6, 2008
posted by cgc373 at 8:14 AM on January 6, 2008
My wife still has the old safari on the old OS, and last night I noticed several blogs were crashing or throwing up minute-long beachballs with unresponsive script errors.
posted by mathowie (staff) at 8:43 AM on January 6, 2008
posted by mathowie (staff) at 8:43 AM on January 6, 2008
I'm glad I'm not the only one noticing a distinct upturn in Safari-crashing websites. Admittedly, I'm running an older version but, up until a few months ago, I rarely ran into a site that crashed me (other than the occasional FrontPage-created messes)
The other day, I discovered that www.intuit.com would consistently crash me.
The voices in my head suggest that some Webkit-unfriendly whoop-te-doo web-2.0 tech has suddenly become popular and is spreading, leading to a lot of crashes for Safari-users.
posted by Thorzdad at 10:18 AM on January 6, 2008
The other day, I discovered that www.intuit.com would consistently crash me.
The voices in my head suggest that some Webkit-unfriendly whoop-te-doo web-2.0 tech has suddenly become popular and is spreading, leading to a lot of crashes for Safari-users.
posted by Thorzdad at 10:18 AM on January 6, 2008
I'm glad I'm not the only one noticing a distinct upturn in Safari-crashing websites. Admittedly, I'm running an older version but, up until a few months ago,
for what it's worth, Safari 2.0.x is a POS. Absolute. Piece. Of. Shit. Well, maybe not, but it is my sworn enemy. I feel sorry for you mac users, because FF is also a flaming hunk of shit on the mac.
the new Safari is much more tolerable of bad javascript and html although it still has that terrible apple skin disease.
I think what you're seeing is the devs who even bother to test with safari are now only testing with the latest safari (i know I got let off the hook on a couple significant bugs when .. whatever the new cat version is .. came out) and aren't catching all the crap that is failing on safari 2.0.x. Additionally, devs who think they can test with safari on the PC are testing with the latest version as well (apple didn't release a 2.0 for the PC, it went straight to 3.0 beta).
upgrading will probably fix everything.
posted by fishfucker at 11:19 AM on January 6, 2008
Thanks for all the adds. I don't know what's weird about my setup over here. Oh well, I'm about to kick it to the curb following the upcoming Macworld announcements. My 2002 iMac has had a good long run, but it's showing its age.
I agree... Safari 3 hasn't been a good build (same build as jamaro... 3.0.4 523.12.12). Maybe it runs differently in Leopard, whose requirements are too steep for this iMac (I have plenty of RAM, but apparently the processor is too slow.)
posted by emelenjr at 11:22 AM on January 6, 2008
I agree... Safari 3 hasn't been a good build (same build as jamaro... 3.0.4 523.12.12). Maybe it runs differently in Leopard, whose requirements are too steep for this iMac (I have plenty of RAM, but apparently the processor is too slow.)
posted by emelenjr at 11:22 AM on January 6, 2008
...for what it's worth, Safari 2.0.x is a POS. Absolute. Piece. Of. Shit. Well, maybe not, but it is my sworn enemy. I feel sorry for you mac users, because FF is also a flaming hunk of shit on the mac.
LOL
I'm running 1.3.2 under 10.3.9. But, like I said, until recently, it's been pretty good for most websites. As for FF...I'm running 2.0.0.11 and find it pretty stable, if clunky in places.
posted by Thorzdad at 12:39 PM on January 6, 2008
LOL
I'm running 1.3.2 under 10.3.9. But, like I said, until recently, it's been pretty good for most websites. As for FF...I'm running 2.0.0.11 and find it pretty stable, if clunky in places.
posted by Thorzdad at 12:39 PM on January 6, 2008
I had some unexpected Safari crashes with MeFi and other sites until I ran the re-released security update. If you haven't installed Security Update 2007-009 v1.1 give it a shot, because v1.0 of that patch did something Very Wrong.
posted by mumkin at 3:38 PM on January 6, 2008
posted by mumkin at 3:38 PM on January 6, 2008
You are not logged in, either login or create an account to post comments
posted by SeizeTheDay at 7:20 AM on January 6, 2008