Re: Crash in terminate: on Mavericks
Re: Crash in terminate: on Mavericks
- Subject: Re: Crash in terminate: on Mavericks
- From: Quincey Morris <email@hidden>
- Date: Mon, 21 Jan 2019 10:07:23 -0800
On Jan 21, 2019, at 09:39 , James Walker <email@hidden> wrote:
>
> I used LLDB, and said
>
> env NSZombieEnabled=YES
>
> before starting the process.
You should turn on zombies from the Diagnostics panel of your target’s scheme,
or (as Ken suggested) use Instruments.
> The backtrace doesn't show any of my code, …
Er, it sure looks like it does:
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 ??? 0x000000010c3013e6 0 + 4499444710
…
> 17 com.apple.AppKit 0x00007fff93342783 NSApplicationMain +
> 940
> 18 ??? 0x00000001034e3f10 0 + 4350426896
> 19 ??? 0x0000000102e3e034 0 + 4343455796
Lines 0, 18 and 19 look like locations in your code, unsymbolicated.
> …so I'm not sure how to proceed
You could try symbolicating the crash log.
> 3 com.apple.AppKit 0x00007fff93355e79 -[NSApplication
> windows] + 17
> …
> 6 com.apple.AppKit 0x00007fff935d7347 -[NSApplication
> terminate:] + 1671
So, your application appears to be terminating, and as part of that process
something seems to be happening with windows, likely closing of windows. It’s
extremely easy to get into an order-of-deallocation problem with views, view
controllers, delegates and other objects, leading to a dangling pointer to an
unallocated object. It’s also extremely for common that the timing differs by
macOS version, which means it might crash in some versions, not in others.
_______________________________________________
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