Re: Report Conflict: Leaks vs. MallocDebug
Re: Report Conflict: Leaks vs. MallocDebug
- Subject: Re: Report Conflict: Leaks vs. MallocDebug
- From: Chris Outwin <email@hidden>
- Date: Tue, 24 Jan 2006 15:11:24 -0600
Thank you for your reply.
MallocDebug reports no leak with the following loop:
- (void)awakeFromNib {
int x;
for (x = 0; x < 10000; x++) {
[self showPanel:nil];
}
}
However, when this loop is commented-out, and
- (IBAction)showPanel:(id)sender {
if (!panelController) {
panelController = [[PanelController alloc] init];
}
[panelController showWindow:self];
}
Is used to manually display the panel by selecting ShowPanel from the
main menu, the 12 byte leak appears in MallocDebug.
The NSImageView subclass is created by dragging a Custom View from
the IB palette and changing its class in the inspector. This is the
only item the NSPanel contains.
Even when I add an outlet in my NSWindowController subclass to my
NSImageView subclass, and include:
- (void)windowWillClose:(NSNotification *)aNotification {
[view release];
}
This is incorrect, unless the view is a top level item in the nib
file.
Malloc debug still reports a 12 byte leak. Leaks reports no
leak. Could someone please help me?
If you call this method 1.000.000 times, does the memory footprint
of your application grow or not?
j o a r
_______________________________________________
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