An Azure service that integrates speech processing into apps and services.
MicrosoftCognitiveServicesSpeech-iOS:1.47.0
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
#37
0 libc++abi.dylib __cxa_get_exception_ptr +88
1 libc++abi.dylib __cxa_throw +92
2 libc++.1.dylib std::__1::__throw_system_errorabi:ne190102 +92
3 libc++.1.dylib std::__1::__throw_system_error(int, char const*) +32
4 libc++.1.dylib std::__1::mutex::lock() +40
5 MicrosoftCognitiveServicesSpeech GetModuleObject
6 libsystem_c.dylib __cxa_finalize_ranges +480
7 libsystem_c.dylib exit +32
8 BackBoardServices __28-[BKSHIDEventObserver _init]_block_invoke_3 +100
9 BoardServices __31-[BSServiceConnection activate]_block_invoke.182 +124
10 BoardServices __61-[BSXPCServiceConnectionEventHandler _connectionInvalidated:]_block_invoke +196
11 BoardServices BSXPCServiceConnectionExecuteCallOut +240
12 BoardServices -[BSXPCServiceConnectionEventHandler _connectionInvalidated:] +180
13 libdispatch.dylib _dispatch_call_block_and_release +32
14 libdispatch.dylib _dispatch_client_callout +16
15 libdispatch.dylib _dispatch_lane_serial_drain +740
16 libdispatch.dylib _dispatch_lane_invoke +440
17 libdispatch.dylib _dispatch_lane_serial_drain +332
18 libdispatch.dylib _dispatch_lane_invoke +440
19 libdispatch.dylib _dispatch_root_queue_drain_deferred_wlh +292
20 libdispatch.dylib _dispatch_workloop_worker_thread +540
21 libsystem_pthread.dylib _pthread_wqthread +292
22 libsystem_pthread.dylib start_wqthread +8
An Azure service that integrates speech processing into apps and services.
MicrosoftCognitiveServicesSpeech-iOS:1.47.0
The stack trace shows a std::__1::mutex::lock() throwing std::__1::__throw_system_error, which indicates a C++ std::system_error coming from a mutex operation inside MicrosoftCognitiveServicesSpeech::GetModuleObject during process teardown (__cxa_finalize_ranges / exit). This is happening on a background thread when the app is going to background/being torn down.
From the available context, the only actionable guidance is to treat this as an unhandled exception/crash coming from a native library and ensure it is captured and diagnosable via a crash-reporting SDK:
MicrosoftCognitiveServicesSpeech and correlate it with app lifecycle events (e.g., backgrounding, deallocation of speech objects).If the app uses App Center Crashes already, the callbacks described in the documentation (willSendErrorReport, didSucceedSendingErrorReport, didFailSendingErrorReport) can be used to verify that the crash report is successfully sent and to attach any additional diagnostic data (for example, current speech SDK state) via attachments(with:for:) before the stored crash is uploaded on next launch.
References: