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: Jeff Johnson <email@hidden>
- Date: Wed, 05 Jun 2013 20:03:22 -0500
On Jun 4, 2013, at 12:35 PM, Jens Alfke <email@hidden> wrote:
> On Jun 4, 2013, at 8:30 AM, Jeff Johnson <email@hidden> wrote:
>
>> The "end" of the event loop cycle is immediately before the beginning. Thus, for example, if your app is in the background and not receiving events, then the autorelease pool will not be drained.
>
> You can work around this by wrapping your own autorelease pools around code that allocates significant amounts of memory, rather than relying on the runloop’s outer autorelease pool to free it for you.
>
> —Jens
In some cases, yes, although the architecture sometimes makes that difficult. 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.
-Jeff
_______________________________________________
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