Search Issue Tracker
Fixed
Fixed in 2021.3.31f1
Votes
0
Found in
2021.3.17f1
Issue ID
UUM-30040
Regression
Yes
Crash in audiomixerruntime.cpp when loading AudioMixer assetbundles built prior to 2021
Open the repro project and play SampleScene to potentially reproduce. Also try a standalone player. The repro loads a scene bundle built in 2019 which contains an audio source and mixer with filters. The repro is not 100% reliable as it depends on uninitialized memory to crash.
* Try using a locally produced build of the Editor.
The issue is that AudioMixerConstant::groupConnectionCount was added in [https://github.cds.internal.unity3d.com/unity/unity/commit/7a6177bf9aef9da594bc283e0663b1781af93b5d] but was not default initialized. If the loaded asset doesn't contain this it may end up with an undefined value.
You can force reproduce the crash by default-initializing groupConnectionCount to a high value to mock-up possible memory state.
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
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
Resolution Note (fix version 2021.3.31f1):
Added default initialisation of a member variable that would be garbled when loading asset bundles that were created before the variable was introduced, causing a crash from illegal memory access.