On 1/18/07, Sebastian Winkler <[EMAIL PROTECTED]> wrote: > While I'm not sure if Camino is actually leaking, it certainly isn't > overly well behaved in its memory consumption habits. > After closing all windows after 9 hours of usage it still comes in at > 115MB while it only occupies 30MB when freshly launched.
There's nothing at all wrong with that. First, Cocoa usually loads things on first use rather than initially. Lots of the system frameworks pull things from disk into memory as they are needed, but then cache them for future use. Second, the idea that closing all windows should release all memory is based on the assumption that all memory use is per window/page, when in reality there's a whole lot of application-wide caching. For instance, the in-memory data structures that handle the on-disk page and image caches aren't flushed just because there are no windows. Keeping things in memory that there is a strong expectation that users will use again is good for performance in general. The alternative is doing tons of extra disk reads and writes, which are monumentally slower. The idea that an app that uses more memory after use than it does at launch is a leak or otherwise an indication of a problem is an unfortunately widely held belief. _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
