Well, I posted my other msg before I saw your reply... but I guess
you're right, it would explain the unreliable results I am getting...
I'll trust Instrument on that one! :)
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?...
On 20-Nov-08, at 4:35 PM, Nick Zitzmann wrote:
On Nov 20, 2008, at 2:10 PM, Jean-Nicolas Jolivet wrote:
However it seems like something is not getting released properly...
I'm looking at Activity Monitor and the memory usage is climbing
fast each time I click the preview button... (like 2-3mb each
time)...
Is there a better way to do it?
Do not pay attention to Top or Activity Monitor when it comes to
leak hunting. They can be misleading, because RAM may not be freed
immediately for performance reasons. Use Instruments or MallocDebug
instead.
Nick Zitzmann
<http://www.chronosnet.com/>
Jean-Nicolas Jolivet
[EMAIL PROTECTED]
http://www.silverscripting.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
