On Apr 1, 2012, at 11:38 AM, Martin Hewitson wrote: > I've received a crash report from a customer which I'm unable to reproduce > and have not heard of from any other user. The action needed for the customer > to reproduce the crash is such a common one, that it seems that all other > customers should hit the same issue. That makes me wonder if it's a problem > of the customer's machine. The crash log is below. > > Does anyone have any suggestions as to how I might find the problem?
> *** Terminating app due to uncaught exception 'NSInvalidArgumentException', > reason: '-[NSRecursiveLock popoverDidClose:]: unrecognized selector sent to > instance 0x1020e2a80' This suggests a memory management bug. Something is invoking -popoverDidClose: on an NSRecursiveLock, which surely isn't what was supposed to receive that message. Usually this happens because the object that was supposed to receive it has been deallocated and another object (an NSRecursiveLock, in this case) has reused that memory. The particular memory management bug may be an over-release (or failure to retain), but it could also be a failure to unregister an object from observing a notification prior to its deallocation. In this case, it seems as though you failed to unset the delegate of the NSPopover prior to the delegate's deallocation. (The NSPopover registers the delegate as an observer of NSPopoverDidCloseNotification and would unregister it when you unset the delegate.) Regards, Ken _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
