Talk:Mac OS X 10.5.2 Fixes, Bugs and Problems

From Mac Guides

(Unverified) Safari still appears to have a memory leak. After 30 minutes of browsing, memory usage exceeds 250 mb. (White 17" iMac C2D 2.0, 3 gb ram).

This is not a leak. Leak is defined as a non-referenced piece of memory (we lost the pointer to it and have no way to address it). When you run leaks command on Safari (Terminal) you'll find out there's just a few small leaks (every app has some - some are in AppKit itself) - don't do this with a 300MB usage though - try it with e.g. 150MB first.

According to the engineering team (see webkit.org) this memory are cached uncompressed images - just the raw data - in case you go back to the web page, so it loads more quickly. I guess that's reasonable in an unreasonable way. I have already filed a bug report asking to either cap the cache or let the users cap it in the Advanced preferences.

However, just as anywhere, there sure are leaks in WebKit, but those leak just a few bytes maybe a MB, not 250MB...

Important: If you think your case is not just huge memory usage, run the leaks command (leaks Safari >> Safari.txt -- this will save the leaks to a Safari.txt file) and file it at http://www.webkit.org - for developers to develop, someone has to test the stuff and report back. More info here: http://webkit.org/quality/leakhunting.html