Re: Does [NSApp setApplicationIconImage] leak memory?
Re: Does [NSApp setApplicationIconImage] leak memory?
- Subject: Re: Does [NSApp setApplicationIconImage] leak memory?
- From: Matt Neuburg <email@hidden>
- Date: Sun, 10 Aug 2008 05:15:35 -0700
- Thread-topic: Does [NSApp setApplicationIconImage] leak memory?
On Sat, 9 Aug 2008 15:19:08 -0700, "Shawn Erickson" <email@hidden>
said:
>On Sat, Aug 9, 2008 at 2:46 PM, Mark Allan <email@hidden> wrote:
>
>> I fail to see how [NSApp setApplicationIconImage:theNewImage]; is any
>> different to [NSApp setApplicationIconImage:[theNewImage objectAtIndex:1]]
>> but it obviously does function differently.
>
>Please post a complete code example that shows the original issue. I
>assure you the change that you stated that corrected the issue isn't
>the thing that corrected (of course you have only been posting partial
>code snippets and descriptions so we don't have the full context).
Also it might be useful to state how you "know" there is or is not a "leak"
in the first place. Is the phenomenon truly that an object remains
incorrectly in memory as revealed by Shark or MallocDebug or similar - and
if so, what object? - or is it merely intuition based on a high-level
virtual memory measurement like Activity Monitor? m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
One of the 2007 MacTech Top 25: <http://tinyurl.com/2rh4pf>
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
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