Report Conflict: Leaks vs. MallocDebug
Report Conflict: Leaks vs. MallocDebug
- Subject: Report Conflict: Leaks vs. MallocDebug
- From: Chris Outwin <email@hidden>
- Date: Tue, 24 Jan 2006 13:37:39 -0600
MallocDebug 1.6.1 (78.0) is reporting a leak that Leaks doesn't in my
app, and I don't know which to believe. I have looked for 5 days to
find info about this leak which is associated with adding a second
window to an app. Nothing I've found addresses the leak.
My non-document, Cocoa app has an AppController allocated in
MainMenu.nib. The AppController allocates (and later releases in
dealloc) a NSWindowController subclass that acts as the file owner
for a second nib which contains a NSPanel. The panel contains a
NSImageView subclass. The NSImageView subclass contains only:
- (id)initWithFrame:(NSRect)frame {
self = [super initWithFrame:frame];
if (self) {
}
return self;
}
- (void)drawRect:(NSRect)rect {
[super drawRect:rect];
}
MallocDebug reports a 12 byte leak when [super drawRect:rect] is
included. No leak is reported when [super draw...] is excluded.
Leaks reports no leak in either case.
Even when I add an outlet in my NSWindowController subclass to my
NSImageView subclass, and include:
(In myWindowController.m)
- (void)windowWillClose:(NSNotification *)aNotification {
[view release];
}
Malloc debug still reports a 12 byte leak. Leaks reports no leak.
Could someone please help me?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden