Hi,
if you think you've found a memory leak inside of CoreAnimation,
please file a radar (bugreporter.apple.com) with a project showing the
leak, and we'll look into it. thanks,
John
On Jun 1, 2008, at 10:58 AM, Stéphane Droux wrote:
On Sun, Jun 1, 2008 at 6:31 PM, Brian Christen
On Sun, Jun 1, 2008 at 6:31 PM, Brian Christensen <[EMAIL PROTECTED]> wrote:
>
> 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
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 never
completing before a new one gets added, so they're just stacking up
on
top of each other.
I don't think
On Sun, Jun 1, 2008 at 3:18 PM, Jonathan del Strother <
[EMAIL PROTECTED]> 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 o
On 6/1/08, Stéphane Droux <[EMAIL PROTECTED]> wrote:
> 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
>>
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 the
On Sun, Jun 1, 2008 at 1:15 PM, Gustavo Eulalio <[EMAIL PROTECTED]> wrote:
> Well, I'm novice to Cocoa/ObjC programming, so, I might be wrong. But
> I see you're setting a new frame on l2 every time fromTimer: is
> called, but you never release the old one. The following may solve it,
> if that's
On Jun 1, 2008, at 5:03 , Stéphane Droux wrote:
I've changed the timer function to do random animations and this
time it
really "leaks":
- (void) fromTimer: (NSTimer *) t
{
l2.frame = CGRectMake((double)random() / RAND_MAX*30,
(double)random() /
RAND_MAX*30, (double)random() / RAND_MAX*
Well, I'm novice to Cocoa/ObjC programming, so, I might be wrong. But
I see you're setting a new frame on l2 every time fromTimer: is
called, but you never release the old one. The following may solve it,
if that's the problem.
- (void) fromTimer: (NSTimer *) t
{
[l2.frame release]
l2.fram
On Sun, Jun 1, 2008 at 8:49 AM, Brian Christensen <[EMAIL PROTECTED]> wrote:
> On Jun 1, 2008, at 2:55 , Stéphane Droux wrote:
>
> When I run the program in Mallocdebug, it seems that one of the threads
>> used
>> by Core Animation to animate the layers doesn't release its memory.
>> So it looks
On Jun 1, 2008, at 2:55 , Stéphane Droux wrote:
When I run the program in Mallocdebug, it seems that one of the
threads used
by Core Animation to animate the layers doesn't release its memory.
So it looks like a bug in Core Animation. However, since animating
non-leaf
layers is such a core f
On Sat, May 31, 2008 at 11:14 PM, Brian Christensen <[EMAIL PROTECTED]>
wrote:
> On May 31, 2008, at 16:39, "Stéphane Droux" <[EMAIL PROTECTED]>
>
> > When I run the program in MallocDebug, the memory usage goes up every
> time the timer function is executed. If I change the animation to be on l2
On May 31, 2008, at 16:39, "Stéphane Droux" <[EMAIL PROTECTED]>
> When I run the program in MallocDebug, the memory usage goes up
every time the timer function is executed. If I change the animation
to be on l2 instead of l1, or if I create l2 as a sublayer of
mainLayer, the memory usage re
Hi,
I'm currently writing an app that creates a complex hierarchy of CALayers.
Everytime I animate one of the layers, I get a memory leak.
In order to investigate the issue, I created a simple Cocoa project in which
I only added a CustomView and the following code for this view :
@implementation
14 matches
Mail list logo
