On Jun 4, 2013, at 12:35 PM, Jens Alfke <[email protected]> wrote: > On Jun 4, 2013, at 8:30 AM, Jeff Johnson <[email protected]> > 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 protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
