IL2CPP crash in UnityMain thread on Android

Hello,

Our game on Android is facing a lot of crashes. The stack trace found on Play Console points to the crash being in the UnityMain thread. Does anyone have

Exception java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version     : 2021.3.4f1
Device model      : samsung SM-N975F
Device fingerprint: samsung/d2sxx/d2s:12/SP1A.210812.016/N975FXXU8HVGA:user/release-keys
Build Type        : Release
Scripting Backend : IL2CPP
ABI               : arm64-v8a
Strip Engine Code : true

Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2021.3.4f1 (cb45f9cae8b7)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'samsung/d2sxx/d2s:12/SP1A.210812.016/N975FXXU8HVGA:user/release-keys'
Revision: '24'
ABI: 'arm64'
Timestamp: 2022-09-19 17:04:31+0200
pid: 27045, tid: 27150, name: UnityMain  >>> cricketgames.hitwicket.strategy <<<
uid: 10752
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6e6f6900000004
    x0  006e6f6900000004  x1  0000000000000001  x2  0000000000000000  x3  0000000000000010
    x4  0000000000000000  x5  0000000000000000  x6  0000000000000000  x7  00000000034ebc74
    x8  00000000b098c770  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
    x12 00000000e9c49b1e  x13 00000000632884fe  x14 001e5c9a4c1bac30  x15 0000336466758982
    x16 000000799c0392a0  x17 0000007d3e5858e8  x18 0000007910c315d8  x19 0000000000000000
    x20 006e6f6900000004  x21 006e6f6900000000  x22 0000000000000001  x23 000000788bc2ffc0
    x24 0000000000000000  x25 0000000040000000  x26 000000799c1da248  x27 000000799c1c6e50
    x28 000000799c1a6388  x29 00000079b1c35380
    sp  00000079b1c35380  lr  00000079985ebdc0  pc  0000007d3e5858f0

backtrace:
      #00 pc 00000000000b58f0  /apex/com.android.runtime/lib64/bionic/libc.so (pthread_mutex_lock+8) (BuildId: eb0c8b7f827292af83855e89b431276a)
      #01 pc 0000000000f97dbc  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libil2cpp.so (BuildId: ec9b805516a89aa10077960ec78d1b51aefa1432)
      #02 pc 000000000333d8ac  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libil2cpp.so (BuildId: ec9b805516a89aa10077960ec78d1b51aefa1432)
      #03 pc 0000000000fe0e3c  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libil2cpp.so (BuildId: ec9b805516a89aa10077960ec78d1b51aefa1432)
      #04 pc 0000000000fe0c9c  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libil2cpp.so (BuildId: ec9b805516a89aa10077960ec78d1b51aefa1432)
      #05 pc 0000000000356aec  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libunity.so (BuildId: d2f5e964a43ad4687a4f958559213b20e952a8c1)
      #06 pc 0000000000364be8  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libunity.so (BuildId: d2f5e964a43ad4687a4f958559213b20e952a8c1)
      #07 pc 0000000000288864  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libunity.so (BuildId: d2f5e964a43ad4687a4f958559213b20e952a8c1)
      #08 pc 00000000003e1620  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libunity.so (BuildId: d2f5e964a43ad4687a4f958559213b20e952a8c1)
      #09 pc 00000000003f7c1c  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/lib/arm64/libunity.so (BuildId: d2f5e964a43ad4687a4f958559213b20e952a8c1)
      #10 pc 000000000009c02c  /data/app/~~dl6kB_rqGI1uWoBMEgpF5A==/cricketgames.hitwicket.strategy-sYnmXxnRuRJm-atcMoeXlA==/oat/arm64/base.odex
  at libc.pthread_mutex_lock (pthread_mutex_lock:8)
  at libil2cpp
  at libil2cpp
  at libil2cpp
  at libil2cpp
  at libunity
  at libunity
  at libunity
  at libunity
  at libunity
  at base

a clue as to what might be happening?

I think that you will need to symbolicate this crash report to find out more details about it. You can find some instructions about how to do that here: https://support.unity.com/hc/en-us/articles/115000292166-Symbolicate-Android-crash