... and of course the getter is
-(id)delegate .. no *, writing on my iPhone on the subway,
can't copy the code from my mac directly.
> Getter is pretty ordinary
>
> -(id*)delegate
> {
> return _delegate;
> }
>
> So in this case A has a strong reference to B and is B's delegate, fairly
Getter is pretty ordinary
-(id*)delegate
{
return _delegate;
}
So in this case A has a strong reference to B and is B's delegate, fairly
common pattern. A is now being deallocated and as part of that the delegate
relationship is being broken, one of two ways, either in A's dealloc it ca
On Sat, 24 Dec 2011 13:35:07 +0800, Roland King said:
object being dealloced. This line of code
>
>return self.delegate == delegateArg
>
>caused self to get a retain/autorelease, resurrecting the object. The change
>to use the ivar directly fixed it
Using the ivar directly is also a way of
.. and of course having asked the question I found the answer.
First, to track it down, I used allocations in instruments, set to track all
objects and enable zombies. Cycling through one time I got the dialog telling
me I'd sent release to a zombie and got the full history.
The message was m
I can't find this one. I have a crash in my app, message being sent to
deallocated instance. I enabled zombies and get the following (first line is a
log in the dealloc() method of my object, second one is from the zombies
framework).
2011-12-24 12:23:04.317 Hippo[17279:fb03] HIPTopicView 0x6b6
