FROM : Stéphane Droux
DATE : Sun Jun 01 16:28:31 2008
On Sun, Jun 1, 2008 at 3:18 PM, Jonathan del Strother <
<email_removed>> 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 never
> completing before a new one gets added, so they're just stacking up on
> top of each other.
>
I don't think they should stack up. Core animation default duration is 0.25
second and these animations are triggered every 0.4 secs.
Anyway, I added a timer to invalidate the first one after 60 seconds. The
memory usage only became constant. It was about 60% more than when the
application started. No memory was released.
DATE : Sun Jun 01 16:28:31 2008
On Sun, Jun 1, 2008 at 3:18 PM, Jonathan del Strother <
<email_removed>> 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 never
> completing before a new one gets added, so they're just stacking up on
> top of each other.
>
I don't think they should stack up. Core animation default duration is 0.25
second and these animations are triggered every 0.4 secs.
Anyway, I added a timer to invalidate the first one after 60 seconds. The
memory usage only became constant. It was about 60% more than when the
application started. No memory was released.






Cocoa mail archive

