Garmin Express Service output reflects normal startup:
2020-04-24 08:48:01.658 Garmin Express Service[558:17246] Garmin Express Service 6.21.0.0 has started.
2020-04-24 08:48:01:661 Garmin Express Service[558:50f] Garmin Express Service 6.21.0.0 has started.
...
2020-04-24 08:48:06:756 Garmin Express Service[558:1203] ANT status host:CONNECTED INITIALIZED ping:0 state:Idle
2020-04-24 08:48:06:756 Garmin Express Service[558:1203] ANT status host:CONNECTED INITIALIZED ping:0 state:BackgroundSearch
2020-04-24 08:48:12:673 Garmin Express Service[558:50f] IPCServer: Registering client
Everything works fine for hours, when suddenly:
2020-04-24 15:48:36:831 Garmin Express Service[558:1203] ANT status host:CONNECTED UNINITIALIZED ping:0 state:Idle
The Garmin Express app shows no connection to the ANT stick and eventually crashes.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
...
Thread 9 Crashed:
0 com.garmin.renu.service 0x000000010d65a5fd DSIANTDevice::ConnectToDevice() + 79
1 com.garmin.renu.service 0x000000010d65af9e DSIANTDevicePolling::RequestThread() + 134
2 com.garmin.renu.service 0x000000010d65aea1 DSIANTDevicePolling::RequestThreadStart(void*) + 9
3 libsystem_pthread.dylib 0x00007fff984fd99d _pthread_body + 131
4 libsystem_pthread.dylib 0x00007fff984fd91a _pthread_start + 168
5 libsystem_pthread.dylib 0x00007fff984fb351 thread_start + 13
...
Thread 9 crashed with X86 Thread State (64-bit):
rax: 0x8000000000000000 rbx: 0x00007fcec365a360 rcx: 0x00000000000fc080 rdx: 0x000000000008cfc0
rdi: 0x00007fcec36649c0 rsi: 0x00007fcec36649c0 rbp: 0x0000700000080eb0 rsp: 0x0000700000080e60
r8: 0x0000000000000000 r9: 0x00007fcec3655c20 r10: 0x00000000bc18dd70 r11: 0x00007fcec3600000
r12: 0x00000000000008ff r13: 0x000000000001178b r14: 0x00007fcec365a440 r15: 0x00007fcec365a508
rip: 0x000000010d65a5fd rfl: 0x0000000000010202 cr2: 0x000000010dd29004
The Mac OS X 10.11.6 (15G22010) System Report USB section lists the ANT stick as usual and no suspicious events are in /var/log/system.log. Rebooting restores full functionality but is inconvenient; are there any alternatives to addressing the symptom if not correcting the problem?