Re: KVO persists too long
Re: KVO persists too long
- Subject: Re: KVO persists too long
- From: Keary Suska <email@hidden>
- Date: Sun, 01 Jul 2007 12:54:25 -0600
- Thread-topic: KVO persists too long
on 6/30/07 9:12 PM, email@hidden purportedly said:
> I'm not retaining it. Nor am I allocating it, copying it, or otherwise know
> anything about its existence.
Actually, you are, just not the specific object you think is the culprit,
which probably isn't. The likely culprit is one of your own objects that you
have told the UI to observe.
> As best as I can tell it's something in the UI
> that's adding itself as an observer and then failing to remove itself. For
> sake of argument, NSZombieEnabled confirmed:
>
> 2007-06-30 21:22:29.843 Debtinator[12459] *** Selector
> 'observeValueForKeyPath:ofObject:change:context:' sent to dealloced instance
> 0x5238640 of class NSKeyValueObservationForwarder. Incidentally, I'm not
> quite sure where that class comes from, since the actual object returned by
> observationInfo is:
>
> <NSKeyValueObservance: Observer: 0x5238640, Key path: apr, Include old: NO,
> Include new: NO, Context: 0x4903d0, Property: 0x5241620>
Here is your clue. What object has the property named "apr"? Are you sure it
isn't being prematurely released (released before the UI is done with it)?
Another consideration: are you doing any manual nib loading?
Best,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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