Re: CoreImage: Newbie can't find memory leak [SOLVED
Re: CoreImage: Newbie can't find memory leak [SOLVED
- Subject: Re: CoreImage: Newbie can't find memory leak [SOLVED
- From: Scott Ellsworth <email@hidden>
- Date: Wed, 15 Feb 2006 07:01:16 -0800
On Feb 14, 2006, at 6:22 PM, Chris Lewis wrote:
You did not allocate aImage or overlayImage IN THIS METHOD.
Therefore you should not release or autorlease aImage or overlayImage
IN THIS METHOD.
You know, that was exactly why I didn't do it in the first place. It
felt like a bad idea at the time :)
I got so excited I'd fixed it (it's seriously been about 8 hours of
screwing around, until it all finally clicked when I used
OmniObjectMeter, and really started *understanding*) I wanted to stop
other people on the list worrying about it :) The releases seemed
coupled to the setValue:, hence why I tried it there.
I strongly suggest getting a copy Accesorizer, and letting it
generate accessors for instance variables. This will make _sure_
that your releases and retains are balanced outside the class. Then,
always use the accessor methods to manipulate the instance variables
from your instance methods - even init and dealloc - and you are safe
from that potential source of mismatched release/retain messages.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden