| [AD] [ alleg-Bugs-2986726 ] Nested autorelease pools ok in native iphone image loader? |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: noreply@xxxxxxxxxx
- Subject: [AD] [ alleg-Bugs-2986726 ] Nested autorelease pools ok in native iphone image loader?
- From: "SourceForge.net" <noreply@xxxxxxxxxx>
- Date: Tue, 13 Apr 2010 20:26:06 +0000
Bugs item #2986726, was opened at 2010-04-13 14:26
Message generated for change (Tracker Item Submitted) made by trentg
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: Open
Resolution: None
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?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2986726&group_id=5665