On Jun 21, 2009, at 18:36:55, Kyle Sluder wrote:
On Sun, Jun 21, 2009 at 5:56 PM, Rick Mann<[email protected]>
wrote:
Is there also a way to tell Core Data to release objects it has
currently
allocated?
After you've read the documentation mmalc pointed you at, also take a
look at the section "Turning Objects into Faults" in the Faulting and
Uniquing section of the Core Data Programming Guide:
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdFaultingUniquing.html#/
/apple_ref/doc/uid/TP30001202-185436-TPXREF147
Also read "Reducing Memory Overhead":
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdPerformance.html#/
/apple_ref/doc/uid/TP40003468-SW4
But don't worry about this until you've demonstrated a memory problem
in your app. You're more likely to hit this on the phone than on the
desktop, to be sure, but it's still not worth the effort optimizing
memory usage that doesn't threaten to pose a problem.
Thanks for the pointers. My "didReceiveMemoryWarning" methods are
being called, so I'm researching various methods to reduce the need to
keep stuff in memory.
--
Rick
_______________________________________________
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]
