On Jun 1, 2008, at 10:28 , Stéphane Droux wrote:
If you kill the timer after its been running for a while, does the memory usage drop back down? Maybe the implicit animations are nevercompleting before a new one gets added, so they're just stacking up ontop of each other.I don't think they should stack up. Core animation default duration is 0.25second and these animations are triggered every 0.4 secs.Anyway, I added a timer to invalidate the first one after 60 seconds. Thememory usage only became constant. It was about 60% more than when the application started. No memory was released.
I would consider that to be expected behavior. If you aren't ever releasing the layers you created, why would any of the relevant memory be freed? The timer and the animations it is causing to be performed should not really be incurring a very significant memory footprint in addition to what the layers on their own are already using (my own observations at least indicate that running the test app with or without the timer makes very little difference in that regard).
Are the two methods you posted really the only two methods in your entire test app? Or are you doing something else somewhere in addition to this? Feel free to e-mail me the test project off-list if you like.
/brian
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
