-
Notifications
You must be signed in to change notification settings - Fork 3
Description
@Zubius Hello,
I am receiving crash reports in the Objective-C part of the plugin, reports from Crashlytics are as follows:
EXC_BAD_ACCESS 0x3f7fffea3ad378d1
Crashed: CHMetricsDispatchQueue
0 libobjc.A.dylib 0x3a9c objc_release + 8
1 libobjc.A.dylib 0x3a9c objc_release_x0 + 8
2 CoreFoundation 0x6e394 -[__NSDictionaryI dealloc] + 152
3 CoreHaptics 0x21a1c -[CHMetrics sendDetailedMetricsForPlayerID:endTime:] + 1724
4 CoreHaptics 0x7520 __44-[CHMetrics handleFinishedForPlayersAtTime:]_block_invoke + 172
5 CoreHaptics 0x75d0 __29-[CHMetrics dispatchOnLocal:]_block_invoke + 44
6 libdispatch.dylib 0x637a8 _dispatch_call_block_and_release + 24
7 libdispatch.dylib 0x64780 _dispatch_client_callout + 16
8 libdispatch.dylib 0x3f6fc _dispatch_lane_serial_drain$VARIANT$armv81 + 600
9 libdispatch.dylib 0x401b0 _dispatch_lane_invoke$VARIANT$armv81 + 380
10 libdispatch.dylib 0x49f14 _dispatch_workloop_worker_thread + 608
11 libsystem_pthread.dylib 0x1bd0 _pthread_wqthread + 284
12 libsystem_pthread.dylib 0x1720 start_wqthread + 8
I only use transient and json haptics, mostly json. Most of the time, there are multiple json haptic patterns playing simultaneously. It's not uncommon for me to start different patterns a few times in a single frame.
Also noticed that the crashes mostly occur on devices in a low RAM state.
Any ideas?
Thanks!