On Sun, Jun 1, 2008 at 1:40 PM, Brian Christensen <[EMAIL PROTECTED]> wrote:
> > Even with this new code I'm still not observing any leaking. Are you using > garbage collection? With GC enabled you will observe fluctuations until the > collector gets a chance to free up unused memory, but even then after a few > minutes or so the usage level should periodically return to a reduced level. > > I am not privy to the caching Core Animation is doing internally, but also > keep in mind that it maintains both presentation and model layers behind the > scenes, in addition to whatever internal caching might be happening to > improve performance. > > What kind of hardware are you running? I suspect we may be seeing some > differences in our results based on that (perhaps different graphics > hardware is causing Core Animation to have to do more - or different - work > on your machine). I still don't see why this would be leaking on your > machine though. > > /brian > > I was running it without garbage collection. I recompiled it with Garbage collection and get the exact same problem. I let it run for 5 minutes and the memory usage keeps increasing. Even if there are fluctuations, the general trend is up and it never does down. Regarding the internal mechanisms of Core Animation, the items in MallocDebug seem to show that the memory is eaten by the Rendering tree, which is a bit worrying since it's a private part of Core Animation on which I don't think I can do anything. I run it on a Macbook (first model). The integrated GC might a reason for Core Animation to use more cache/memory, but I don't see why this memory would keep increasing. _______________________________________________ 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]
