Re: Core Data app becomes a memory hog
Re: Core Data app becomes a memory hog
- Subject: Re: Core Data app becomes a memory hog
- From: "Joshua Pennington" <email@hidden>
- Date: Fri, 8 Jun 2007 09:35:00 -0500
The problem was due to the way autoreleasing objects works. When an
object receives an -autorelease message, it is added to the current
autorelease pool. The default autorelease pool is emptied (all objects
in it are sent -release) once every execution of the run loop - in
some cases, that is not often enough and it is necessary to create
another one that will be "emptied" sooner, in order to not have so
many objects taking up memory while waiting to be autoreleased.
On 6/8/07, Clint Shryock <email@hidden> wrote:
anyone care to detail what was causing the problem and why this solution
fixed it? is it a problem with autorelease pool itself, or how it were
being used?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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