On 08/01/2007, at 5:43 AM, Mars Saxman wrote:
On Jan 7, 2007, at 2:11 PM, Andy Dent wrote:
If so, you may be able to load from that memory block and thus
avoid the automatic reference that causes the leak.
It is not a leak; the data is only loaded once. Subsequent
references reuse the same picture object.
Sorry, leak was the wrong term. "Picture allocation with reference
that can't be removed".
As this is a non-issue for most apps, I imagine there's little
likelihood of it changing.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
