Unity fmod 2.01.11 crash on android

Unity
1

Has No Has Big Old Met FMOD 2.01.11 Crash On Mi Mobile Phone While Opening the Setting Bellow

设置–声音与触感–声音助手–多应用媒体音调节
image

Crash After

FMODUnity.RuntimeUtils:GetCurrentPlatform()
    FMODUnity.RuntimeManager:Initialize()
    FMODUnity.RuntimeManager:get_Instance()
    FMODUnity.RuntimeManager:LoadBank(String, Boolean)
    FmodAudioMgr:Init()
    FmodAudioMgr:Get(GameObject)
    FmodAudioMgrWrap:Get(IntPtr)

2022-01-17 16:18:36.608 1182-1182/? E/CRASH: signal 11 (SIGSEGV), code 0 (?), fault addr 000028140000049e
2022-01-17 16:18:36.608 1182-1182/? E/CRASH: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2022-01-17 16:18:36.608 1182-1493/? E/CRASH: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 00000075a862a110
2022-01-17 16:18:36.608 1182-1493/? E/CRASH: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2022-01-17 16:18:36.608 1182-1182/? E/CRASH: Build fingerprint: 'Xiaomi/cupid/cupid:12/SKQ1.211006.001/V13.0.10.0.SLCCNXM:user/release-keys'
2022-01-17 16:18:36.608 1182-1182/? E/CRASH: Revision: '0'
2022-01-17 16:18:36.609 1182-1493/? E/CRASH: Build fingerprint: 'Xiaomi/cupid/cupid:12/SKQ1.211006.001/V13.0.10.0.SLCCNXM:user/release-keys'
2022-01-17 16:18:36.609 1182-1493/? E/CRASH: Revision: '0'
2022-01-17 16:18:36.609 1182-1182/? E/CRASH: pid: 1182, tid: 1182, name: ***.m4399  >>> com.******.m4399 <<<
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x0   fffffffffffffffc  x1   0000007ff83f2ac0  x2   0000000000000010  x3   0000000000000045
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x4   0000000000000000  x5   0000000000000008  x6   000000001391d4d8  x7   0000000000000010
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x8   0000000000000016  x9   0000000000000000  x10  000000764b79e000  x11  00000000000000e0
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x12  000000000000000c  x13  000000003f9914f8  x14  00000000013d70cc  x15  000007579b7a0655
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x16  00000078ce3f6d50  x17  00000078da30aba4  x18  00000000df0628e6  x19  000000765b79a770
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x20  000000765b79a818  x21  0000000000000045  x22  0000000000000045  x23  000000765b79a770
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x24  000000007fffffff  x25  00000078e2b59000  x26  0000000014ec0000  x27  00000075eb7b3430
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     x28  000000007087cc90  x29  0000007ff83f2bd0  x30  00000078ce3f2eac
2022-01-17 16:18:36.609 1182-1182/? E/CRASH:     sp   0000007ff83f2a80  pc   00000078da34abcc  pstate 0000000060001000
2022-01-17 16:18:36.609 1182-1182/? E/CRASH: backtrace:
2022-01-17 16:18:36.609 1182-1493/? E/CRASH: pid: 1182, tid: 1493, name: Binder:1182_4  >>> com.***********.m4399 <<<
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x0   000000000000e000  x1   00000078ce332dd0  x2   0000000000000000  x3   000000751ab0c388
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x4   0000000000000138  x5   000000765b7a5e10  x6   00000000000000dd  x7   0000000000000000
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x8   00000075a862a100  x9   585c8e8c555f6a85  x10  0000000000000000  x11  000000004c000000
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x12  000000004c000000  x13  0000000000000000  x14  0000000000000003  x15  0000000000000000
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x16  00000078d9ebda28  x17  00000078be267a18  x18  0000007504d12000  x19  00000076bb9f0180
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x20  00000076bb9f0508  x21  00000000e000e000  x22  000000765b9a76b0  x23  000000751ab0e000
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x24  000000751ab0e000  x25  000000768b7bcda4  x26  0000000000000000  x27  000000000000049e
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     x28  0000000000000000  x29  000000751ab0d670  x30  00000078ce301044
2022-01-17 16:18:36.609 1182-1493/? E/CRASH:     sp   000000751ab0c5c0  pc   00000078ce30104c  pstate 0000000060001000
2022-01-17 16:18:36.609 1182-1493/? E/CRASH: backtrace:
2

This appears to be a feature (“multi-app media sound adjustment”) that only exists on certain Android phones. I can see that certain models of Xiaomi Mi and Samsung Galaxy phones have it but not all.

I will create a bug report, but in the meantime, it would be good to have an FAQ or known issues for players that have this feature on their phone to know to turn it off if they are experiencing crashes.

3

Our development team is asking if you could provide the crash logs from using the logging version of FMOD for Unity (libfmodstudioL.so) so we can investigate further?

4

sorry, I just came back from spring festival,I don’t have this phone now because it was leased from player. we let players known that have this feature on their phone and turn it off if they are experiencing crashes.