Re: Lion document opening: -[__NSArrayM insertObject:atIndex:]: object cannot be nil
Re: Lion document opening: -[__NSArrayM insertObject:atIndex:]: object cannot be nil
- Subject: Re: Lion document opening: -[__NSArrayM insertObject:atIndex:]: object cannot be nil
- From: Benjamin Rister <email@hidden>
- Date: Fri, 05 Aug 2011 14:21:55 -0400
By the way, if any Apple people want to take a look, it's rdar://9896209
Best,
br
On Jul 25, 2011, at 2:17 PM, Benjamin Rister wrote:
> We have an agent (UIElement) process, using GC, that can open a custom document type. Other than it being an agent, there’s nothing particularly special going on.
>
> On Lion, when one of these documents are opened, the window appears, but then the application promptly has an uncaught exception and crashes. The difficult matter here is that there’s no code of ours in the stack trace involving the exception, it just looks like internal NSDocumentController machinery, and everything works fine on 10.6. So while as a first pass this looks like it could be a Lion bug, I thought I’d run it past the hive mind here to see if anybody has seen any issues like it themselves and have any insight into a workaround or anything that we could be doing wrong to be causing it.
>
> *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
> *** First throw call stack:
> (
> 0 CoreFoundation 0x00007fff8882f986 __exceptionPreprocess + 198
> 1 libobjc.A.dylib 0x00007fff8a38ad5e objc_exception_throw + 43
> 2 CoreFoundation 0x00007fff887d6818 -[__NSArrayM insertObject:atIndex:] + 296
> 3 AppKit 0x00007fff8d47d242 __-[NSApplication(NSAppleEventHandling) _handleAEOpenDocumentsForURLs:]_block_invoke_2 + 1089
> 4 AppKit 0x00007fff8d581b85 __-[NSDocumentController _openDocumentsWithContentsOfURLs:presentErrors:completionHandler:]_block_invoke_2 + 50
> 5 Foundation 0x00007fff88add581 -[NSBlockOperation main] + 116
> 6 Foundation 0x00007fff88aa40b0 -[__NSOperationInternal start] + 705
> 7 Foundation 0x00007fff88ab73d2 ____NSOQSchedule_block_invoke_2 + 124
> 8 libdispatch.dylib 0x00007fff8ca6d90a _dispatch_call_block_and_release + 18
> 9 libdispatch.dylib 0x00007fff8ca6f77a _dispatch_main_queue_callback_4CF + 308
> 10 CoreFoundation 0x00007fff887c4c0c __CFRunLoopRun + 1724
> 11 CoreFoundation 0x00007fff887c4216 CFRunLoopRunSpecific + 230
> 12 HIToolbox 0x00007fff92b0a4ff RunCurrentEventLoopInMode + 277
> 13 HIToolbox 0x00007fff92b11c21 ReceiveNextEventCommon + 355
> 14 HIToolbox 0x00007fff92b11aae BlockUntilNextEventMatchingListInMode + 62
> 15 AppKit 0x00007fff8d1c1191 _DPSNextEvent + 659
> 16 AppKit 0x00007fff8d1c0a95 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
> 17 AppKit 0x00007fff8d1bd3d6 -[NSApplication run] + 463
> 18 AppKit 0x00007fff8d43b52a NSApplicationMain + 867
> 19 Synk Agent 0x00000001000020ec Synk Agent + 8428
> 20 ??? 0x0000000000000001 0x0 + 1
> )
>
> Any insight or info would be appreciated.
>
> Best,
> Benjamin Rister
_______________________________________________
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