Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.62f1
6000.2.10f1
6000.3.0b4
Issue ID
UUM-126803
Regression
No
[Windows] Crash on AudioManager::InitFMOD when performing various actions in the Editor
A crash in the Unity Editor has been observed affecting various workflows including:
- Returning to the Editor after the computer falls asleep
- Unplugging headphones while a Quest device is connected
- Unplugging headphones after disconnecting a Quest device
- Turning off headphones while the Editor is open
- A Quest device falls asleep while the Editor is open
Reproducible with: 6000.0.62f1, 6000.2.0b1 - 6000.2.10f1, 6000.3.0a3 - 6000.3.0b4
Reproduced on: Windows 10, Windows 11 (user devices)
Not reproduced on: No other environment tested
Note: Not reproduced by CQA
First few lines of the stack trace:
0x00007FF80FDF66CA (KERNELBASE) RaiseException
0x00007FFF44E78696 (Unity) LaunchBugReporter
0x00007FFF447715BF (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFF447720E0 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFF4541CAFD (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFF4541BE79 (Unity) DebugStringToFile
0x00007FFF4413B6BD (Unity) AudioManager::InitFMOD
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
Add comment