Search Issue Tracker
Fixed
Fixed in 2022.3.45f1, 6000.0.22f1, 7000.0.0a1
Votes
14
Found in
2022.3.36f1
6000.0.14f1
Issue ID
UUM-76489
Regression
Yes
Android crashes in fmod after upgrading from 2022.3.24 to 2022.3.36
A user updated from 2022.3.24 to 2022.3.36 and now has issues with fmod on Android. They’re seeing new crashes in Firebase with the following stack trace:
{{FMOD::DSPI::disconnectAllInternal(bool, bool, bool) (??:0)}}
{{FMOD::UserFile::reallyAsyncRead(FMOD_ASYNCREADINFO*, unsigned int*, bool) (??:0)}}
{{FMOD_vorbis_synthesis_blockin (??:0)}}
Note: CQA could not reproduce this issue due to no project and reproduction steps being present.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
- Crash on EditorApplication:Internal_CallUpdateFunctions when pushing property block by index to SpriteShapeRenderer
darrin5698
Aug 24, 2024 09:55
The stack trace indicates issues related to FMOD, specifically within the disconnectAllInternal, reallyAsyncRead, and vorbis_synthesis_blockin functions. These functions are part of FMOD's internal operations related to disconnecting DSP nodes, handling asynchronous file reads, and Vorbis decoding.
Potential Causes
FMOD Update Compatibility: The update from version 2022.3.24 to 2022.3.36 might have introduced changes in FMOD's API or behavior, especially if the FMOD integration wasn't updated alongside Unity.
File Handling/Async Read: The reallyAsyncRead function suggests that there may be issues related to how FMOD handles asynchronous reads of audio files, particularly Vorbis-encoded files.
DSP Graph Issues: The disconnectAllInternal function indicates that there might be problems with disconnecting DSP (Digital Signal Processing) nodes within FMOD, potentially leading to crashes if certain nodes are left in an inconsistent state.
Suggested Actions
FMOD Integration Update: Ensure that the FMOD integration in the project is up to date and compatible with the updated Unity version. Check if FMOD's version is supported by Unity 2022.3.36.
Vorbis File Handling: Investigate any Vorbis-encoded files being used in the project. Ensure they are correctly formatted and that FMOD's Vorbis support is properly configured.
Logging & Debugging: Enable detailed logging in FMOD to capture more information about what's causing the crash. This may help identify specific files or operations that trigger the issue.
Test on Different Devices: Since CQA couldn't reproduce the issue, test on various Android devices to check if the problem is device-specific or only occurs under certain conditions.
FMOD Forum/Support: If the issue persists, reaching out to FMOD's support team or forums with the stack trace and more context might provide additional insights or patches.
Revert Changes (Temporary Fix): If the issue is critical and you cannot resolve it immediately, consider reverting to version 2022.3.24 until a solution is found.
Would you like assistance with any of these steps?
jg_ed
Aug 22, 2024 09:29
Same problem
artem_kalytiuk_42
Aug 21, 2024 14:04
Hi, I too ran into this error the other day.
German-Krasnikov
Aug 21, 2024 13:57
Hi, I have same problem