Re: another n00b question -- how to find a memory leak
Re: another n00b question -- how to find a memory leak
- Subject: Re: another n00b question -- how to find a memory leak
- From: "Shawn Erickson" <email@hidden>
- Date: Wed, 22 Oct 2008 14:00:58 -0700
On Wed, Oct 22, 2008 at 1:46 PM, John Zorko <email@hidden> wrote:
>
> Bill,
>
> Alas, I found it 10 minutes after I posted the message *sigh* ... I forgot
> the autorelease pool in my override of
> -observeValueForKeyPath:ofObject:change:contet: ... the console message is
> gone now :-)
>
Humm that has me concerned... it usually isn't a good idea for KVO to
be fired from a secondary thread (since often UI, etc. can be involved
and often that isn't safe to be doing from a secondary thread). You
likely should be bouncing KVO triggering operations to the main
thread.
-Shawn
_______________________________________________
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