Re: NSImageView and releasing it's images...
Re: NSImageView and releasing it's images...
- Subject: Re: NSImageView and releasing it's images...
- From: Nick Zitzmann <email@hidden>
- Date: Thu, 20 Nov 2008 14:50:57 -0700
On Nov 20, 2008, at 2:43 PM, Jean-Nicolas Jolivet wrote:
From what I can see... it seems like OS X (or BSD or whatever
manages that) will use a lot of memory if it has a lot of memory
available (I have 4gb)... and use less if it has less... I might be
wrong about that but it seems to be working that way from what I can
tell... (which is a bit different than what I'm used to on Windows
using Task Manager)... It seems like linux behaves like that
too...and it would also explain why Activity/Top etc.. aren't really
"reliable" ways of determining an App's memory usage... (i.e. it
might use more memory if you have more available)... am I right to
think that?...
Yes. Lots of physical RAM usage is good, up to a point, because it's
more expensive for an application to grow a zone than it is for it to
recycle unused RAM in a a zone. You shouldn't ever worry about what
you're worrying about, unless your program has nearly hit its VM limit
(in which case it is OK to panic).
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden