Search Issue Tracker
Fixed
Fixed in 6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
6000.4.0a1
Issue ID
UUM-109545
Regression
No
Crash on AudioMixer::GetFloat when entering Play Mode in a specific project
How to reproduce:
1. Open the attached “CrashRepro“ project
2. Open the “Assets/Scenes/MainMenu.unity“ Scene
3. Enter Play Mode
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 10 (by user)
Not reproducible on: No other environment tested
Note: Project can also crash when opening it
First few lines of the stack trace:
0x00007ff6f6e12f90 (Unity) AudioMixer::GetFloat
0x00007ff6f5bd8fee (Unity) AudioMixer_CUSTOM_GetFloat
0x0000018031b69567 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Audio.AudioMixer:GetFloat (UnityEngine.Audio.AudioMixer,string,single&)
0x0000018031b68d7b (Mono JIT Code) LocalAudioManager:Start () (at E:/Unity/Unity Projects/RIcochet-REload/Assets/Scripts/LocalAudioManager.cs:104)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment