Re: Problems with object observing own key

FROM : Mike Abdullah
DATE : Mon May 12 00:09:29 2008

This is a general problem with KVO when observing self. As I 
understand, Apple has recognised the issue though and for apps linked 
or run on Leopard (one of the 2) the system should be intelligent 
enough to not print warnings. The best alternative I can suggest is to 
override -release so that you can sneak some kind of -willDealloc 
method in before the actual de-allocation and subsequent warnings.

Mike.

On 11 May 2008, at 22:53, Colin Cornaby wrote:

> But see, that's the thing. My objects dealloc method fires AFTER the 
> warning appears, so my object hasn't actually been deallocated yet.
>
> In the deallocation my object removes the observers from itself. If 
> my object was actually deallocating first, I should be getting this 
> message.
>
> I'll do some poking around, but I don't think this is a memory 
> management issue. Wouldn't be the first time I've had to eat my 
> words though. :p
>
> On May 11, 2008, at 2:47 PM, Kyle Sluder wrote:
>

>> On Sun, May 11, 2008 at 5:19 PM, Colin Cornaby 
>> <colin.<email_removed>> wrote:

>>> #0      0x94eb4993 in NSKVODeallocateBreak
>>> #1      0x94e267c4 in NSKVODeallocate
>>> #2      0x94d7d57f in NSPopAutoreleasePool
>>> #3      0x945b1e54 in -[NSApplication run]
>>> #4      0x9457f030 in NSApplicationMain
>>> #5      0x00008208 in main at main.m:13

>>
>> See stack frame #2?  You should immediately have recognized that you
>> have a memory management issue on your hands.  You're failing to
>> retain the object somewhere.
>>
>> --Kyle Sluder

>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>