SpokesSDK crash on 10.13

15 posts / 0 new

Fri, 10/27/2017 - 03:34

vikkolesnyk

SpokesSDK crashes in InitSpokesRuntime() on MacOS 10.13. Works OK in 10.11 and 10.12. Crash is in USBRawDevice_Monitor_Thread, when main thread executes InitSpokesRuntime() Please find part of MacOS crash log below: OS Version: Mac OS X 10.13 (17A405) Report Version: 12 Crashed Thread: 10 USBRawDevice_Monitor_Thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY Thread 0:: Dispatch queue: hid.queue 0 libsystem_kernel.dylib 0x00007fff744ec1d2 __semwait_signal + 10 1 libsystem_c.dylib 0x00007fff74467774 nanosleep + 199 2 Plantronics-Inc..Spokes3GSDK 0x00000001038c3787 boost::this_thread::no_interruption_point::hiden::sleep_until(timespec const&) + 183 3 Plantronics-Inc..Spokes3GSDK 0x0000000103913637 HIDAL_DeviceNotification::DoGetAllAttachedHIDDevicesPath() + 275 4 Plantronics-Inc..Spokes3GSDK 0x00000001039134e9 invocation function for block in HIDAL_DeviceNotification::GetAllAttachedHIDDevicesPath() + 41 5 libdispatch.dylib 0x00007fff74362f64 _dispatch_client_callout + 8 6 libdispatch.dylib 0x00007fff743763f2 _dispatch_queue_barrier_sync_invoke_and_complete + 60 7 Plantronics-Inc..Spokes3GSDK 0x0000000103913418 HIDAL_DeviceNotification::GetAllAttachedHIDDevicesPath() + 202 8 Plantronics-Inc..Spokes3GSDK 0x000000010391c776 hidal_get_all_paths() + 78 9 Plantronics-Inc..Spokes3GSDK 0x0000000103a7662a DeviceManager::getDevicesImpl(IDeviceGroup**, boost::function, std::__1::allocator >)>) + 72 10 Plantronics-Inc..Spokes3GSDK 0x0000000103a76980 DeviceManager::getDevices(eVendorID, IDeviceGroup**) + 150 11 Plantronics-Inc..Spokes3GSDK 0x00000001039f8e00 Plantronics::CallManager::GetAllConnectedDevices() + 92 12 Plantronics-Inc..Spokes3GSDK 0x00000001039e5b30 Plantronics::CallManager::AttachToAllConnectedDevices() + 62 13 Plantronics-Inc..Spokes3GSDK 0x00000001039e3067 Plantronics::CallManager::AttachToAnyDevice() + 55 14 Plantronics-Inc..Spokes3GSDK 0x00000001039f80b7 Plantronics::CallManager::Init(ISessionManager*) + 701 15 Plantronics-Inc..Spokes3GSDK 0x0000000103a10d34 SessionManager::InitCallManager(IDeviceManager*, INotificationManagerInt*) + 110 16 Plantronics-Inc..Spokes3GSDK 0x0000000103a1095e SessionManager::Init(IDeviceManager*, INotificationManagerInt*) + 106 17 Plantronics-Inc..Spokes3GSDK 0x0000000103a10829 SessionManager::SessionManager(IDeviceManager*, INotificationManagerInt*) + 303 18 Plantronics-Inc..Spokes3GSDK 0x0000000103ad6428 InitSpokesRuntime + 162 ... Thread 10 Crashed:: USBRawDevice_Monitor_Thread 0 com.apple.iokit.IOUSBLib 0x0000000108ff2341 IOUSBIUnknown::genericQueryInterface(void*, CFUUIDBytes, void**) + 11 1 Plantronics-Inc..Spokes3GSDK 0x000000010390f283 -[USBRawDeviceNotificationPrivate rawDeviceAdded:] + 605 2 Plantronics-Inc..Spokes3GSDK 0x000000010390ee85 -[USBRawDeviceNotificationPrivate doStartListen] + 749 3 Plantronics-Inc..Spokes3GSDK 0x000000010390ea31 __46-[USBRawDeviceNotificationPrivate startListen]_block_invoke + 26 4 Plantronics-Inc..Spokes3GSDK 0x0000000103936292 __38+[PltRLThread syncRunBlock:inRunLoop:]_block_invoke + 16 5 com.apple.CoreFoundation 0x00007fff4ce5752c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 6 com.apple.CoreFoundation 0x00007fff4ce39f43 __CFRunLoopDoBlocks + 275 7 com.apple.CoreFoundation 0x00007fff4ce39d08 __CFRunLoopRun + 3128 8 com.apple.CoreFoundation 0x00007fff4ce38e43 CFRunLoopRunSpecific + 483 9 Plantronics-Inc..Spokes3GSDK 0x0000000103935e1e -[PltRLThreadPrivate doThread] + 293 10 Plantronics-Inc..Spokes3GSDK 0x0000000103935cbf PltRLThreadCallback::rl_thread_callback(void*) + 45 11 libsystem_pthread.dylib 0x00007fff746266c1 _pthread_body + 340 12 libsystem_pthread.dylib 0x00007fff7462656d _pthread_start + 377 13 libsystem_pthread.dylib 0x00007fff74625c5d thread_start + 13

Fri, 10/27/2017 - 03:57

lcollins

Hi, Thanks for bringing this to our attention. We are already aware of the issue and it is being actively investigated, although the cause is not yet known. Could you confirm if your Mac has only USB-C ports (2016 or newer model), and if you are using an Apple or 3rd party adaptor (USB-C to USB-A)? Thanks, Lewis.

Fri, 10/27/2017 - 06:31

(Reply to #2) #3

vikkolesnyk

Lewis, Thank you for quick reply. Yes, Mac has only USB-C ports. And yes, 3rdParty adaptor is using.

Fri, 10/27/2017 - 06:41

(Reply to #3) #4

lcollins

Hi, thanks, so we are still trying to qualify this issue. Could you confirm the make/model of your adaptor?

Mon, 10/30/2017 - 03:21

(Reply to #4) #5

vikkolesnyk

Hi. Adaptor is no-name (China), sorry. Also I tried on older Mac with 10.13, that has direct USB-A port. And it didn't not crash on it either on init or during work with Bluetooth Headset. We are at pre-releasing stage of our product with Spokes3G support introduced for MacOS and I'm in doubts now what is better to totally disable 'Spokes3G' on MacOS > 10.12 as it will cause app to crash on Init for 2016 or newer Macs or enable it and try to catch exception as seems it does not crash on 2015 and older Macs even on 10.13. Bad thing is that crash is not in Spokes3G thread, whether our app could catch crash from, but in child USB thread.

Mon, 11/06/2017 - 14:27

mattyv123

I stumbled upon this thread as I am having the exact same issue on my mac, only with the latest version of the Plantronics Hub software installed on macOS 10.13.1. I've been having this crash since I started using the macOS 10.13 beta, but Plantronics support wouldn't help because it wasn't GA yet.  Now that it is released, the problem still exists.  The app opens and immediately closes without showing any menu bar icons or etc.  A crash report is generated, much like the one above.  I am running a MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports), on 10.13.1. Please let me know how I can help troubleshoot this problem.

Thu, 11/09/2017 - 02:24

(Reply to #6) #7

vikkolesnyk

mattyv123, In my case Plantronics Support provided me with beta version of Spokes3G SDK with fix included and this resolved issue. I'm waiting for official release though.

Wed, 11/22/2017 - 09:39

(Reply to #7) #8

lcollins

Hi, The next Plantronics Hub release 3.10.2 planned for week of December 11th will contain the fix for this issue. Thanks, Lewis.

Tue, 12/12/2017 - 02:34

(Reply to #8) #9

EdgeSystems

What's the status? We need the update ASAP.

Tue, 12/12/2017 - 07:08

(Reply to #9) #10

lcollins

Hi, The fix with the release was due this week of Dec 11 and this still may happen, otherwise it may be Mon 18th Dec. Thanks, Lewis.

Wed, 12/13/2017 - 02:23

(Reply to #10) #11

EdgeSystems

Thanks! :)

Tue, 12/19/2017 - 01:56

(Reply to #11) #12

EdgeSystems

Btw, what has the hub to do with that the SDK crashes? Can you update the SDK page as well: ( http://developer.plantronics.com/softphone-integration-sdks )

Tue, 12/19/2017 - 03:49

(Reply to #12) #13

lcollins

Hi, It's the same root cause - the SDK and Hub share the same software stack. As soon as the 3.10.2 is available the SDK page will also be updated...

Tue, 12/19/2017 - 04:10

(Reply to #13) #14

EdgeSystems

Fyi: Hub version 3.10.2 is available and the new  sdk is bundled through it but the sdk download page isn't updated.

Tue, 12/19/2017 - 05:54

(Reply to #14) #15

lcollins

Thanks for the heads up SDK page now up to date <a href="/softphone-integration-sdks">http://developer.plantronics.com/softphone-integration-sdks</a> To match corresponding Hub builds for Windows and Mac.

Add new comment