On Sep 24, 2015, at 10:02 AM, Jens Alfke <j...@mooseyard.com> wrote: > > This is a pretty common type of crash. You’ve got an NSTableView whose > dataSource has been dealloced, so it tried to call the dataSource and crashed. > If you want to catch this in the debugger, turn Zombie Objects on. > Most likely the problem is that the window got closed but not released, so it > and its views are still in memory.
There's another possibility: Switching from older SDK to 10.9 or 10.10 (I forget which) changed some order of operations. Used to be: once window controller -close was called, everything went dead, and you could tear down table views, controllers, delegates, data sources in pretty much any order you wanted. The new way: the frigging thing will try to redraw itself after -close, actually after invoking willClose on its window controller, and you have to tear things down in a very specific order. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ https://www.linkedin.com/in/scottribe/ (303) 722-0567 voice _______________________________________________ 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
