Re: Memory not being released in a timely manner
Re: Memory not being released in a timely manner
- Subject: Re: Memory not being released in a timely manner
- From: Graham Cox <email@hidden>
- Date: Thu, 06 Jun 2013 11:42:12 +1000
On 06/06/2013, at 11:03 AM, Jeff Johnson <email@hidden> wrote:
> In some cases, yes, although the architecture sometimes makes that difficult.
Can you give an example?
> And even code that allocates only a small amount of memory can become very significant if it is called repeatedly over the course of the app's running for days or weeks at a time.
That would surely be a leak? That's quite different from just being slow to autorelease something. An app that runs for weeks without once spinning its run loop? And if that's the case, it's your responsibility to use autorelease pools correctly.
--Graham
_______________________________________________
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