On Oct 1, 2008, at 12:57 PM, Christopher J Kemsley wrote:
I neglected to mention in my original post that, when this object is
deallocated, it explicitly deallocated the editedRowName before
calling a [super dealloc], so the thing should be deallocated.
By that I hope you don't mean that you're explicitly calling "-
dealloc"? You shouldn't.
On Oct 1, 2008, at 12:34 PM, Christopher J Kemsley wrote:
However, when I do a "Run with performance tool: Leaks", it tells me
that, ever time this part of the code runs, it leaks a
"GeneralBlock-32" with the following information:
Category: CFString (store)
Event Type: Malloc
Responsible Library: Foundation
Responsible Caller: -[NSCFString mutableCopyWithZone:]
Does anybody know where this leak is coming from?
Note that this is the allocation site for the leaked object. That is
not necessarily the same thing as the place where you introduced the
memory management error that is the reason for the leak. If you use
Instruments to inspect the individual memory management events for
this object you'll likely see a number of retains, release, and
autorelease operations. You'll have to figure out where a unbalanced
call is introduced.
j o a r
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
