[AD] [ alleg-Bugs-2986726 ] Nested autorelease pools ok in native iphone image loader?

[SourceForge.net <noreply@xxxxxxxxxx>]

Bugs item #2986726, was opened at 2010-04-13 13:26
Message generated for change (Comment added) made by elias
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2986726&group_id=5665

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: iPhone
Group: 4.9
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Trent Gamblin (trentg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Nested autorelease pools ok in native iphone image loader?

Initial Comment:
The native iphone image loader is leaking memory without an autorelease pool. I will be adding a short-lived autorelease pool to the loading function, but this fix may cause problems if a user calls the function from a thread that already has an autorelease pool. Are autorelease pools nestable?

----------------------------------------------------------------------

>Comment By: Elias Pschernig (elias)
Date: 2012-01-20 05:33

Message:
Yes and I think by now we removed all global autorelease pools anyway and
always do it with a short-lived one.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2986726&group_id=5665