| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Fri, Aug 8, 2008 at 9:02 AM, Matt Neuburg <email@hidden> wrote:At 6:24 pm -0400 08/08/2008, Sumner Trammell wrote:> m.On Thu, 7 Aug 2008 20:14:04 +0100, Mark Allan <email@hidden> said:Hi all,
Before I file a bug report against this, I just thought I'd check I'm not being monumentally stupid first!
I'm trying to animate my app's Dock icon, which works fine and looks great, but unfortunately, it appears to leak memory like crazy. Every time I call [NSApp setApplicationIconImage:(NSImage *)] and pass it pointer to an existing image, it leaks more memory.
Wrap each call to setApplicationIconImage in an autorelease pool creation and release, like this:
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; [NSApp setApplicationIconImage: whatever]; [pool release];
I think you'll find that solves the problem.
Ok, stupid question time.
1. Is the need for the autorelease pool because of the use of setApplicationIconImage, or because of the array that is being used in conjunction with setApplicationIconImage?
2. Would putting the calls to setApplicationIconImage in a class method also stop the memory leak?
Thanks,
-s
Thanks guys.
M
_______________________________________________
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: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
| References: | |
| >Re: Does [NSApp setApplicationIconImage] leak memory? (From: Matt Neuburg <email@hidden>) | |
| >Re: Does [NSApp setApplicationIconImage] leak memory? (From: "Sumner Trammell" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.