Re: NSAutoreleasePool: how does it really work?
Re: NSAutoreleasePool: how does it really work?
- Subject: Re: NSAutoreleasePool: how does it really work?
- From: Dan Bernstein <cocoa-dev%email@hidden>
- Date: Tue, 18 Mar 2003 23:11:15 +0200
I haven't been following this discussion to closely, but I really think
you'd gain more understanding of what your program is doing with the
memory it consumes if you used tools other than "top". I think "heap"
and ObjectAlloc are good starting points.
-- Dan
On Tuesday, March 18, 2003, at 10:35 PM, Lorenzo Puleo wrote:
Hi Oleg,
the problem is not the 500,000 iterations.
I did that just to see better what was happening.
Also the iterations could be 100,000 and the objects allocated could
be 5
per each iteration...
The problem is that the unix "top" command in the Terminal tells me
that the
RSIZE of my application and the FREE memory don't come back to the
initial
values, after I have released the objects. So I would like to
understand
better what is happening.
Best Regards
--
Lorenzo Puleo
email: email@hidden
From: email@hidden
Reply-To: email@hidden
Date: Tue, 18 Mar 2003 11:27:54 -0800
To: email@hidden
Subject: cocoa-dev digest, Vol 2 #2089 - 10 msgs
How often in the real life do we need loops of 500 000 iterations
where
every step allocates and deallocates ObjC instances?
_______________________________________________
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.
_______________________________________________
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.