Re: NSAutoreleasePool: how does it really work?
Re: NSAutoreleasePool: how does it really work?
- Subject: Re: NSAutoreleasePool: how does it really work?
- From: Lorenzo Puleo <email@hidden>
- Date: Wed, 19 Mar 2003 12:53:51 +0100
Hi Christian,
Thank you. I am relaxed now. After the first MyLoop, if I run again the
routine, the memory doesn't grow anymore. So it's stable. At the first loop
my app memory really grows to 62MB.
Only I hope the other applications can use the memory that my application
doesn't use anymore. I would not like other application should be forced to
use virtual memory because my application memory has grown. But for this,
Bill already answered to this question. They can. See the following reply by
Bill.
>
After your loop has finished running and before you quit the app, the
>
RSIZE doesn't decrease because there is no reason for it too! Mach
>
will only decrease the RSIZE-- the resident working set of memory
>
pages-- if some other application indicates that it needs to increase
>
its RSIZE.
Thank you so much to you and to Bill.
Best Regards
--
Lorenzo Puleo
email: email@hidden
>
From: Christian Longshore Claiborn <email@hidden>
>
Date: Tue, 18 Mar 2003 13:27:26 -0800
>
To: Lorenzo Puleo <email@hidden>
>
Cc: email@hidden
>
Subject: Re: NSAutoreleasePool: how does it really work?
>
>
What you need to watch for is growth; if your routine allocates 8
>
megabytes every time it runs, then you've got a memory leak. If after
>
exercising each portion of your program, your memory footprint is
>
stable, then you're doing fine.
>
>
Christian
_______________________________________________
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.