> On Feb 12, 2016, at 9:46 PM, Graham Cox <[email protected]> wrote: > > >> On 13 Feb 2016, at 10:13 AM, Quincey Morris >> <[email protected]> wrote: >> >> On Feb 12, 2016, at 14:58 , Graham Cox <[email protected]> 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. >> > > > My thoughts exactly, except (I should have mentioned) I’ve been running with > zombies on and this crash occurs still (but only once in a blue moon). I > guess that still could mean it’s some other memory that’s getting clobbered. > The sort of bug I hate, there’s so few ways to get a handle on it.
Is it possible that you might have accidentally accessed something from a background thread? Charles _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
