Re: Why does this leak memory?
Re: Why does this leak memory?
- Subject: Re: Why does this leak memory?
- From: Charilaos Skiadas <email@hidden>
- Date: Sun, 10 Jul 2005 22:31:51 -0500
On Jul 10, 2005, at 10:22 PM, Matt Ball wrote:
No, it doesn't still crash. However, then I have a bunch of memory
leaks...
Yeah, of course. Just wanted to make sure what was it that was
crashing. Question now is why...
And this always happens on the first cell that is populated, or does
it happen after some cells? I.e. does it happen each time one goes
through the methods, or do they managed to run a couple of times first?
Ok, this may sound weird and probably stupid, and maybe it is, but try:
return [[[shadowCanvas autorelease] copy autorelease];
Other than that, I'm afraid I might be out of ideas.
- Matt Ball
On 7/10/05, Charilaos Skiadas <email@hidden> wrote:
Does it still crash if you replace:
return [shadowCanvas autorelease];
With
return shadowCanvas;
??
Also, just to make sure, your setImage does look like this?
- (void)setImage:(NSImage *)anImage
{
if(anImage != image && anImage != nil)
{
[image release];
image = [anImage retain];
}
}
I have to say, your code looks ok now, but maybe someone with more
experience can spot what goes wrong. In general, NSZombieEnabled is
what you want to look into to help you deal with autorelease issues.
This is probably an autorelease issue. That's why your app crashes
whenever the autorelease pool gets a chance to be released, which may
vary.
On Jul 10, 2005, at 9:55 PM, Matt Ball wrote:
Actually, after further experimentation, it doesn't seem to be
consistent on where the NSLogs stop. Sometimes it gets all the
way to
"End drawWithFrame" before crashing...
- Matt Ball
Haris
Haris
_______________________________________________
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