That’s Safari’s it goes

After Monday’s memory manglage, I found Safari having similar memory problems again yesterday – this time it was with a single tab open. Admittedly, the tab in question was the Tiggercam home page, which runs a bit of JavaScript to continuously refresh the webcam image, but I’ve never seen that cause any browser to eat 5GB of RAM and three times that of virtual memory before. It’s possible that it was one of the extensions I’ve been trying, rather than Safari itself that causes the problem, but I’m afraid I really don’t have the time or the inclination to fiddle with things like that these days.

Safari hung yet again when failing to open a web page, and once again required a Force Quit.

And so, I’ve reverted to Firefox, which while it takes a while to start, is a lot better behaved.

I’ll give Safari another try when it gets to version 6 or thereabouts.