Re: Don't you hate it when Appkit crashes?
Re: Don't you hate it when Appkit crashes?
- Subject: Re: Don't you hate it when Appkit crashes?
- From: Quincey Morris <email@hidden>
- Date: Fri, 12 Feb 2016 15:13:25 -0800
- Feedback-id: 167118m:167118agrif8a:167118sGt0F4qaCV:SMTPCORP
On Feb 12, 2016, at 14:58 , Graham Cox <email@hidden> 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 (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