Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.7f1
6000.2.0b5
Issue ID
UUM-108844
Regression
No
Crash on AudioMixer::GetFMODChannelGroup when entering Play Mode in a specific project
How to reproduce:
1. Open the attached “IN-99183_CrashRepro“ project
2. Open the “Assets/Scenes/Gorilla/Gorilla Tag/GorillaTagNewVisualsCosmetics.unity“ Scene
3. Enter Play Mode
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
First few lines of the stack trace:
0x00007ff7bf767124 (Unity) AudioMixer::GetFMODChannelGroup
0x00007ff7bf767e72 (Unity) AudioSource::GetParentGroup
0x00007ff7bf76228c (Unity) AudioSource::ConfigureFMODGroups
0x00007ff7bf7635a8 (Unity) AudioSource::CreateFMODGroups
0x00007ff7bf76d8fd (Unity) AudioSource::PlayOneShot
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The project is using a faulty mixer setup.
Assets/AudioMixerGroupController/Master.asset
Deleting the asset will prevent the crash from happening.
We would need more information on how the lone mixer group asset was created without having a mixer to properly understand and fix this issue.