Uncaught exception on launch


(Rick Darenberg) #1

I’m getting an uncaught exception error on launch of both SD 6 and a trial version of SD 7. I’m not sure if they are the same exception but here’s the console output from SD 6.

7/9/18 22:18:10.396 Script Debugger[9221]: An uncaught exception was raised
7/9/18 22:18:10.396 Script Debugger[9221]: Error -2147450879 received from OSAID instance
7/9/18 22:18:10.397 Script Debugger[9221]: (
0 CoreFoundation 0x00007fff833ab452 __exceptionPreprocess + 178
1 libobjc.A.dylib 0x00007fff8e02373c objc_exception_throw + 48
2 CoreFoundation 0x00007fff833ab399 -[NSException raise] + 9
3 RosieKit2 0x0000000104163976 -[RKOSAID _failOSError:] + 342
4 RosieKit2 0x00000001041664ab -[RKOSAID compileDescriptor:withModeFlags:] + 309
5 Script Debugger 0x0000000103ec8307 -[ScriptDebuggerAppDelegate init] + 2891
6 AppKit 0x00007fff91a13669 -[NSCustomObject nibInstantiate] + 346
7 AppKit 0x00007fff91a134ab -[NSIBObjectData instantiateObject:] + 309
8 AppKit 0x00007fff91a12b2f -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 428
9 AppKit 0x00007fff91a09d8d loadNib + 384
10 AppKit 0x00007fff91a092b3 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300
11 AppKit 0x00007fff91a0907c -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201
12 AppKit 0x00007fff91a08e48 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344
13 AppKit 0x00007fff91a040a2 NSApplicationMain + 466
14 Script Debugger 0x0000000103ec5364 start + 52
)
7/9/18 22:18:10.397 Script Debugger[9221]: *** Terminating app due to uncaught exception ‘RKOSAID Failure’, reason: ‘Error -2147450879 received from OSAID instance’
*** First throw call stack:
(
0 CoreFoundation 0x00007fff833ab452 __exceptionPreprocess + 178
1 libobjc.A.dylib 0x00007fff8e02373c objc_exception_throw + 48
2 CoreFoundation 0x00007fff833ab399 -[NSException raise] + 9
3 RosieKit2 0x0000000104163976 -[RKOSAID _failOSError:] + 342
4 RosieKit2 0x00000001041664ab -[RKOSAID compileDescriptor:withModeFlags:] + 309
5 Script Debugger 0x0000000103ec8307 -[ScriptDebuggerAppDelegate init] + 2891
6 AppKit 0x00007fff91a13669 -[NSCustomObject nibInstantiate] + 346
7 AppKit 0x00007fff91a134ab -[NSIBObjectData instantiateObject:] + 309
8 AppKit 0x00007fff91a12b2f -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 428
9 AppKit 0x00007fff91a09d8d loadNib + 384
10 AppKit 0x00007fff91a092b3 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300
11 AppKit 0x00007fff91a0907c -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201
12 AppKit 0x00007fff91a08e48 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344
13 AppKit 0x00007fff91a040a2 NSApplicationMain + 466
14 Script Debugger 0x0000000103ec5364 start + 52
)
7/9/18 22:18:10.398 diagnosticd[161]: error evaluating process info - pid: 9221, puniqueid: 9221
7/9/18 22:18:10.399 com.apple.xpc.launchd[1]: (com.latenightsw.ScriptDebugger6.156512[9221]) Service exited due to signal: Abort trap: 6
7/9/18 22:18:10.493 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[9223]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
7/9/18 22:18:11.047 lsd[377]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist
7/9/18 22:18:11.375 ReportCrash[9223]: Saved crash report for Script Debugger[9221] version 6.0.8 (6A225) to /Users/rickdees/Library/Logs/DiagnosticReports/Script Debugger_2018-07-09-221811_MacPro.crash
7/9/18 22:18:11.530 ReportCrash[9223]: Failed to write crash history to file:///Users/rickdees/Library/Application%20Support/CrashReporter/Script%20Debugger_D47D6011-F235-5513-94AA-70FF5568498A.plist.
7/9/18 22:18:17.072 com.apple.xpc.launchd[1]: (com.paloaltonetworks.gp.pangpsd[9225]) Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /Applications/GlobalProtect.app/Contents/Resources: 15G22010: xpcproxy + 12068 [1343][FCA6A1D1-235A-3D89-B197-D43C88E22F3F]: 0x2
7/9/18 22:18:17.072 com.apple.xpc.launchd[1]: (com.paloaltonetworks.gp.pangpsd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
7/9/18 22:18:20.627 Mail[3163]: [IMAP] IMAPConnection was lost during processing of command (null): * BYE.
7/9/18 22:18:26.631 Mail[3163]: [IMAP] IMAPConnection was lost during processing of command (null): * BYE.
7/9/18 22:18:27.083 com.apple.xpc.launchd[1]: (com.paloaltonetworks.gp.pangpsd[9226]) Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /Applications/GlobalProtect.app/Contents/Resources: 15G22010: xpcproxy + 12068 [1343][FCA6A1D1-235A-3D89-B197-D43C88E22F3F]: 0x2
7/9/18 22:18:27.083 com.apple.xpc.launchd[1]: (com.paloaltonetworks.gp.pangpsd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
7/9/18 22:18:29.863 com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[9227]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.ipc
7/9/18 22:18:29.863 com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[9227]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.notification

Any help debugging this would be greatly appreciated.


(Mark Alldritt) #2

The crash logs suggest that Script Debugger’s OSA component is not properly installed.

When Script Debugger is launched, it places a file called Script Debugger.component in your ~/Library/Components folder. You can try manually deleting this file and then launch Script Debugger to see if that resolves the problem.

If the Script Debugger.component file is absent from the ~/Library/Components folder then there is some issue with your system preventing Script Debugger from installing Script Debugger.component.

If the problem persists, please download a fresh copy of Script Debugger from our web site (i.e. clear all browser caches before downloading Script Debugger).

Its a long shot, but you can also try restarting your Mac. In some rare instances, this has been known to resolve this issue.