[Worked around] Re: [NSImage initWithData]: Memory leak. Bug in code or in Framework?
[Worked around] Re: [NSImage initWithData]: Memory leak. Bug in code or in Framework?
- Subject: [Worked around] Re: [NSImage initWithData]: Memory leak. Bug in code or in Framework?
- From: Stéphane <email@hidden>
- Date: Fri, 14 Dec 2007 11:21:39 +0100
On Dec 14, 2007, at 3:30 AM, Peter Ammon wrote:
On Dec 13, 2007, at 2:59 PM, Stephane Sudre wrote:
On Dec 13, 2007, at 9:04 PM, Stéphane wrote:
This simple sample code results in a memory leak in [NSImage
initWithData:].
Is it a bug in Cocoa or is it a bug in the code itself?
Is there a workaround (I already tried multiple things:
mutableCopy of data to releaseit after initialization,
setDataRetained and different cache mode for the NSImage).
No useful pointers found in the list archive or on the net.
Note that without the distribution notification communication, it
works fine (this is to illustrate a problem seen in a tool
receiving dist notifications).
It looks like this is a bug in [NSBitmapImageRep
imageRepsWithData:] (apparently the code used by initWithData if I
am to believe the Gnustep source code) or one of its method when
invoked in this mode.
If I delay the initWithData: code with a
performSelector:withObject:afterDelay:, it does not leak.
A re-reading of the NSDistributedNotificationCenter does not
highlight any obvious reason for this leak to happen.
Hi Stephane,
What's going on here is that the autoreleased objects in the
distributed notification callback are being collected by the
outermost autorelease pool, which is only drained when an event is
received. If you add an autorelease pool to your callback, the
"leak" disappears. Also, if you just do something in the app -
say, open a menu - all the "leaked" memory is reclaimed.
So this isn't strictly a leak, but it's worth a bug report
anyways. Please file one. Meanwhile, adding an autorelease pool
to your notification callback is the best workaround.
OK, thanks. It indeeds solve this case. It's an interesting fact to
take into account when working on a tool with no UI.
I will file a bug or enhancement request.
_______________________________________________
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