NSSpellChecker uses DO to connect with the spellchecker process.  It properly 
handles any exceptions that may result, so these exceptions would be caught and 
handled and you do not need to be reporting them.

Douglas Davidson

On Aug 12, 2014, at 5:22 PM, Dragan Milić <mi...@mac.com> wrote:

> I'm getting exception reports from users of an application I'm working on 
> that I cannot reproduce. The exception comes from the NSSpellChecker 
> instance, and the trace looks something like this:
> 
> 
> NSObjectInaccessibleException
> 
> NSDistantObject (0x600002279bc0) is invalid (no connection)
> 
> 0x7fff91c61aee  0x7fff8a9fde75  0x7fff916dd10c  0x7fff92f6d6f9  
> 0x7fff9163b0f4  0x7fff9163aea8  0x7fff89151a0c  0x7fff88cda673  
> 0x7fff88cd8664  0x7fff92ef38a1  0x7fff92ef354b  0x7fff9030c28d  
> 0x7fff9030e673  0x7fff9030f9c1  0x7fff9030df87  0x7fff9030f177  
> 0x7fff8d984ef8  0x7fff8d987fb9
> 
> NSExceptionHandlerExceptionRaiser (in ExceptionHandling) + 172
> objc_exception_throw (in libobjc.A.dylib) + 43
> +[NSException raise:format:] (in CoreFoundation) + 204
> -[NSDistantObject forwardInvocation:] (in Foundation) + 291
> ___forwarding___ (in CoreFoundation) + 452
> _CF_forwarding_prep_0 (in CoreFoundation) + 120
> -[NSSpellChecker 
> _checkSpellingAndGrammarInString:range:enclosingRange:offset:types:options:orthography:inSpellDocumentWithTag:mutableResults:wordCount:]
>  (in AppKit) + 2071
> NSSpellCheckerCheckString (in AppKit) + 8096
> -[NSTextCheckingOperation main] (in AppKit) + 152
> -[__NSOperationInternal _start:] (in Foundation) + 631
> __NSOQSchedule_f (in Foundation) + 64
> _dispatch_client_callout (in libdispatch.dylib) + 8
> _dispatch_queue_drain (in libdispatch.dylib) + 451
> _dispatch_queue_invoke (in libdispatch.dylib) + 110
> _dispatch_root_queue_drain (in libdispatch.dylib) + 75
> _dispatch_worker_thread2 (in libdispatch.dylib) + 40
> _pthread_wqthread (in libsystem_pthread.dylib) + 314
> 
> start_wqthread (in libsystem_pthread.dylib) + 13
> 
> 
> Most of the time it comes from the -[NSSpellChecker 
> _checkSpellingAndGrammarInString:range:enclosingRange:offset:types:options:orthography:inSpellDocumentWithTag:mutableResults:wordCount:]
>  method, but sometimes from -[NSSpellChecker 
> setIgnoredWords:inSpellDocumentWithTag:]. Also, sometimes the exception is 
> NSPortTimeoutException (connection timeout: did not receive reply), but still 
> related to DOs.
> 
> The thing is I don't use NSSpellChecker in the application at all. As 
> expected, there are a lot of NSTextField and a few NSTextView instances, but 
> NSSpellChecker is not used directly. Users say exceptions happen in different 
> situations, but mostly when doing something that requires typing into a text 
> field. I do use distributed objects though, to communicate with external 
> helper tools which execute some certain tasks. Connection objects for that 
> communication are created and destroyed as needed.
> 
> I have created a startup item which runs a DTrace script and prints names and 
> PIDs of processes making any kind of mach_port call, but that didn't give me 
> any clue of why this is happening.
> 
> I've also list's archive and I couldn't find anything related to this, but I 
> hope someone might have a clue of what's really happening here.
> 
> -- Dragan
> 
> 
> -- Dragan
> 
> 
> _______________________________________________
> 
> 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/ddavidso%40apple.com
> 
> This email sent to ddavi...@apple.com


_______________________________________________

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