On Feb 12, 2016, at 14:58 , Graham Cox <graham....@bigpond.com> wrote: > > 0 libobjc.A.dylib 0x00007fff9673e4dd objc_msgSend + 29 > 1 com.apple.QuartzCore 0x00007fff9550eb45 > CA::Layer::setter(unsigned int, _CAValueType, void const*) + 165
Unfortunately, it’s not obvious that it’s an AppKit-caused crash, or anything other than a memory management bug in your code. Think about scenarios. You could have had a reference to an object that you released, causing deallocation. That memory block is re-allocated for something in AppKit, then you accidentally release your unowned reference again. Hilarity pursues. _______________________________________________ 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
