Re: Best way to find memory leaks
Re: Best way to find memory leaks
- Subject: Re: Best way to find memory leaks
- From: Nick Zitzmann <email@hidden>
- Date: Fri, 25 Jun 2004 12:27:08 -0600
On Jun 25, 2004, at 10:07 AM, Ken Tozier wrote:
It's not listed at Apple's documentation site and Google has little of
use for this one. Anyone know how to prevent NSPathStore2 from
leaking?
NSPathStore2 is part of NSString's class cluster, which is why it's not
showing up in the documentation.
To find out the origin of each object in ObjectAlloc, find the category
in the instance browser, and click on an instance. You might have to
double-click on the instance, I'm not sure, but ObjectAlloc does track
the origins of each object, as well as when (and if) it was
deallocated. And if you checked "also record CF & ObjC reference
counting" when you pressed play, you should also see retain &
non-dealloc release events. That should help you track this down.
Nick Zitzmann
<
http://www.chronosnet.com/>
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.