Re: Memory leak when setting CALayer name

Sorry misclicked the reply and reply all button, posting agan on the list On Tue, Mar 24, 2009 at 8:42 AM, Gustavo Adolfo Pizano < gustavxcodepic...@gmail.com> wrote: Ok, let me check the M.M rules once again, there must be something wrong with what im doing. AFter I need no more of a particu

Re: Memory leak when setting CALayer name

On Mar 22, 2009, at 4:19 AM, Gustavo Pizano wrote: So how come Im applying the M.M rules wrongly, what am I missing? :(. If your applying the memory management rules correctly and your still leaking, then there is probably a bug. You should file one at with

Re: Memory leak when setting CALayer name

I have been trying to follow the rules by the book, but somehow all the time there is something that applies in a different way. All the time Im thinking myself if I "own" the object, who should released, is this a copy, etc, so I can decided if its on me to release it or no. I see the

Re: Memory leak when setting CALayer name

If you create a layer with a factory method, then the layer will be released automatically by an NSAutoreleasePool. I suggest you read the rules on Memory Management for Objective-C. I think that the cause of your leak is also in the trend of not knowing the MemoryManagement rules/ not applyi