Re: Solving memory leaks
Re: Solving memory leaks
- Subject: Re: Solving memory leaks
- From: Quincey Morris <email@hidden>
- Date: Sat, 27 Mar 2010 15:16:25 -0700
On Mar 27, 2010, at 14:11, Klaus Backert wrote:
> something like this (caution: typed in mail, etc.)
Yeah, something like this, but *not* this:
> self.myFields = [[NSMutableArray alloc] init];
That's a memory leak right there. :)
Incidentally, I think the OP was mistakenly interpreting Instruments as indicating the point of the leak. Instruments was indicating the place where the leaked object was originally created, which is likely *not* the point of the error. (In fact, there usually isn't a point where the leak occurs -- it occurs because some necessary 'release' was omitted.)
_______________________________________________
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