Safari & VideoSift bad bedfellows
I've noticed a weird (I suppose Flash related) memory leak when using the new FireFox browser on OSX 10.5. It happens after prolonged viewings of Flash video on the site, so I switched to Safari 4.
The memory leak is no longer an issue, but I cannot stay logged in for very long at all. Sometimes I can stay logged in for an hour and other times I can only stay logged on for seconds.
Any of the other few Mac users on here experiencing this issue?
The memory leak is no longer an issue, but I cannot stay logged in for very long at all. Sometimes I can stay logged in for an hour and other times I can only stay logged on for seconds.
Any of the other few Mac users on here experiencing this issue?
7 Comments
I had trouble watching video with Safari back in 2006, so back then I switched to Firefox for most browser activity. At that time it was causing Safari to crash.
bf, I found this David Pogue post that puts the blame on Adobe:
http://pogue.blogs.nytimes.com/2009/07/02/why-do-adobe-flash-videos-slow-down/
^Yeah, it seems to affect OSX FireFox specifically and almost deliberately. It really gets so bad that after a day of viewing (sometimes less) I need to restart otherwise my entire OS slows to a crawl.
Apparently Safari does a decent job of garbage collection for memory leaks, because it doesn't happen when using Safari, but then again I cannot stay logged in.
Flash is so broken these days. It used to be able to use my GPU - not anymore. Now my CPU goes spastic trying to take over, so much so that I had to download a manual fan controller proggy just to keep it from overheating. Oddities, like only certain videos cause the CPU to go nuts (codec related perhaps?), and wild memory leaks. I thought it was Firefox for a while, before getting the same problem in every browser. I miss Macromedia. Fuck Adobe.
Quite possibly found a fix.
So far so good. Maybe it was a set of bad cookies or something, I don't know.
This seems to fix the problem. I was experiencing it on two separate computers, so I imagine it had something to do with updating Safari to the latest without completely deleting cookies or whatever... I seriously don't know. Anyhow, no point keeping this around... *discard
Discarding this post - discard requested by original submitter blankfist.
Discuss...
Enable JavaScript to submit a comment.