> On 20 Aug 2015, at 07:40, Shane Stanley <sstan...@myriad-com.com.au> wrote:
> 
> I'm try to track down a crash, and I'm not sure where to begin. This is what 
> I see:
> 
> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
> 
> Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes:       KERN_INVALID_ADDRESS at 0x000007fb9095d6f0
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> VM Regions Near 0x7fb9095d6f0:
>    CoreAnimation          0000000117933000-0000000117934000 [    4K] rw-/rwx 
> SM=PRV  
> --> 
>    STACK GUARD            0000700000000000-0000700000001000 [    4K] ---/rwx 
> SM=NUL  stack guard for thread 5
> 
> Application Specific Information:
> objc_msgSend() selector name: retain
> 
> 
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   libobjc.A.dylib                   0x00007fff96ee44dd objc_msgSend + 29
> 1   com.apple.CoreFoundation          0x00007fff927b8b59 
> _CFPreferencesSetValueWithContainer + 153
> 2   com.apple.Foundation              0x00007fff91fa30af 
> -[NSUserDefaults(NSUserDefaults) setObject:forKey:] + 46
> 3   com.apple.CoreFoundation          0x00007fff9279ca3f -[NSSet 
> makeObjectsPerformSelector:] + 223
> 4   com.apple.AppKit                  0x00007fff8aa5fd26 -[NSIBObjectData 
> nibInstantiateWithOwner:options:topLevelObjects:] + 1142
> 5   com.apple.AppKit                  0x00007fff8aa3e9c1 loadNib + 384
> 6   com.apple.AppKit                  0x00007fff8aa3dee5 
> +[NSBundle(NSNibLoading) 
> _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300
> 7   com.apple.AppKit                  0x00007fff8abdc7d0 
> +[NSBundle(NSNibLoadingInternal) 
> _loadNibFile:externalNameTable:options:withZone:] + 150
> 8   com.apple.AppKit                  0x00007fff8abdc588 -[NSWindowController 
> loadWindow] + 310
> 9   com.apple.AppKit                  0x00007fff8abd79f3 -[NSWindowController 
> window] + 80
> 10  com.apple.AppKit                  0x00007fff8abe8bf2 -[NSWindowController 
> showWindow:] + 36
> 11  com.apple.AppKit                  0x00007fff8abfffea -[NSDocument 
> showWindows] + 93
> 12  com.apple.AppKit                  0x00007fff8af979dc 
> __80-[NSDocumentController 
> openDocumentWithContentsOfURL:display:completionHandler:]_block_invoke1035 + 
> 200
> 13  com.apple.CoreFoundation          0x00007fff927acaec 
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
> 14  com.apple.CoreFoundation          0x00007fff9279e865 __CFRunLoopDoBlocks 
> + 341
> 15  com.apple.CoreFoundation          0x00007fff9279e02e __CFRunLoopRun + 910
> 16  com.apple.CoreFoundation          0x00007fff9279da38 CFRunLoopRunSpecific 
> + 296
> 17  com.apple.HIToolbox               0x00007fff9a36f3bd 
> RunCurrentEventLoopInMode + 235
> 18  com.apple.HIToolbox               0x00007fff9a36f153 
> ReceiveNextEventCommon + 432
> 19  com.apple.HIToolbox               0x00007fff9a36ef93 
> _BlockUntilNextEventMatchingListInModeWithFilter + 71
> 20  com.apple.AppKit                  0x00007fff8aac01e7 _DPSNextEvent + 1076
> 21  com.apple.AppKit                  0x00007fff8ae8c90d -[NSApplication 
> _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
> 22  com.apple.AppKit                  0x00007fff8aab60b8 -[NSApplication run] 
> + 682
> 23  com.apple.AppKit                  0x00007fff8aa38396 NSApplicationMain + 
> 1176
> 24  libdyld.dylib                     0x00007fff89e345ad start + 1
> 
> It's a document-based app and I can produce it at will by: closing a 
> document, waiting a couple fo seconds, then opening it (or any other 
> document).

You can repro? That’s a great start! Considering it’s a crash in objc_msgSend, 
my first suspicion is a zombie. Try running your app with zombies enabled, or 
using Instruments’ zombie tool and see if that narrows it down at all.
_______________________________________________

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

Reply via email to