On Aug 30, 2010, at 7:35 PM, Rick Mann wrote: > We're having a hard time tracking down our smaller leaks in our iPad app. > When running on the simulator, one thing we noticed is that none of our Core > Data objects shows up in Leaks or Allocations (all of them have custom > NSManagedObject subclasses). > > Does Core Data never actually instantiate our objects, instead somehow > usurping each individual action implementation and instantiating its own kind > of objects? > > Why do we not see NSManagedObject, nor any of our subclasses, in Leaks or > Allocations?
Some from column A, some from column B. CoreData will create custom subclasses of your classes and instantiate those instead of your classes (this shows up if you run heap from the command line). More relevant to your question, CoreData uses a different allocation path than most of the rest of Cocoa with the result that many objects allocated by CoreData (particularly those which are allocated in bulk, like object ids, managed objects, etc) appear in Leaks/Allocations as anonymous malloc blocks. You should be able to play around with allocating extra instances during startup to figure out what block size maps to what managed object class(es). +Melissa _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
