On May 11, 2008, at 2:53 PM, 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
I don't think this is a memory management issue; it's come up before
on the list:
http://lists.apple.com/archives/Cocoa-dev/2006/Jul/msg00009.html
http://lists.apple.com/archives/cocoa-dev//2007/Dec/msg01217.html
Based on other posts, I don't think there's a general solution, other
than to avoid doing this sort of cleanup in -dealloc. I remove/add
observers in viewWillMoveToSuperview for NSView subclasses (which it
looks like you might have?).
hth,
Adam
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
