Re: NSOperation and NSAutoreleasePool
Re: NSOperation and NSAutoreleasePool
- Subject: Re: NSOperation and NSAutoreleasePool
- From: Aaron Wallis <email@hidden>
- Date: Sat, 7 Mar 2009 16:44:19 +1100
I've actually found a workaround - it seems that if I use Obj-C 2.0
style properties the objects somehow get released earlier than they
should.
in my example I used the code:
self.delegate = tDelegate
where tDelegate is the delegate supplied through the method call.
However, if I just use:
delegate = tDelegate
the script runs fine without a hitch...
it must have something to do with the self.delegate property being set
to retain or something?
maybe it's causing the nsautoreleasepool to release early?
On 07/03/2009, at 4:35 PM, Kyle Sluder wrote:
It sounds like you have some sort of memory issue. Since you refer to
things like "NSAutorelease objects" (which don't exist) and are
apparently calling -retain on an object that you immediately assign to
a property, I suggest you go back and re-read the Memory Management
Guide.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden