Re: NSFontPanel swamping the responder chain (and crashing)
Re: NSFontPanel swamping the responder chain (and crashing)
- Subject: Re: NSFontPanel swamping the responder chain (and crashing)
- From: Graham Cox <email@hidden>
- Date: Thu, 21 May 2015 17:18:06 +1000
> On 21 May 2015, at 2:41 pm, Quincey Morris <email@hidden> wrote:
>
> It looks to me like the problem is that the NSWindowController’s “document” property is still set to the NSDocument object that was just deallocated
How did you determine that it’s this property that is stale? The stack trace includes a whole bunch of assembly language, but it’s not directly traceable to that property (or at least I can’t trace it). Is there some Insruments magic I haven’t stumbled across yet?
> I would be inclined to try putting a breakpoint at the -[NSWindow supplementalTargetForAction:sender:] method, and poke around once there. Easier than Instruments, I’d imagine.
Well, trouble is because the Font Panel is calling through this on every single event, it’s breaking all the time. I thought I’d add an action to ‘po self’ but that doesn’t work - self isn’t recognised at this level. I have no idea how to just log the address (or better, the -description) of self and continue.
—Graham
_______________________________________________
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