Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.15f1
6000.0.0b12
Issue ID
UUM-67078
Regression
No
Crash when attempting to create a custom FMOD DSP unit
Reproduction steps:
1. Open the attached “crash_IN-70937“ project
2. Open the “MainScene”
3. Enter the Play Mode
4. Press the “On/Off“ button quickly a few times (usually two is enough) or press it one time and move the slider
5. Observe a crash
Reproduced with: 2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
- Reproducible in Player
- Crash is most likely caused by the “CreateCustomDSP” method, which is in the “Synth” Script
- Crashes without a stack trace
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
In this repro project, Unity Audio is disabled and a 3rd party engine, FMOD, is being used. The crash is related to a custom DSP that the user is creating and hooking into FMOD's graph. This is likely either an issue with the customer's custom DSP or FMOD. It's not likely to be a Unity issue.