Re: NSAutoreleasePool: how does it really work?
Re: NSAutoreleasePool: how does it really work?
- Subject: Re: NSAutoreleasePool: how does it really work?
- From: Andres Santiago Perez-Bergquist <email@hidden>
- Date: Tue, 18 Mar 2003 12:33:20 -0500
On Tuesday, March 18, 2003, at 10:52 AM, Sujal Shah wrote:
Have you verified that your output from top or ps is accurate? In
other
words, written a simple application where you don't autorelease? So,
just write a simple application and verify that your monitoring
methodology is accurate. I seem to remember that those numbers are
flaky at best in terms of accuracy... but, maybe that's just a linux
thing (where most of my experience is...).
Sujal
With some compilers and C-libraries there are multiple layers of
allocation. That is, the library gets big chunks of memory from the
system, and then parcels them out via its own allocation scheme to
malloc, new, and alloc requests. It's possible that's what's happening
here, with memory being freed at an application level but not a system
level.
-- Andres
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.