Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
0
Found in
5.6.1p2
Issue ID
918651
Regression
Yes
[Win] Disabling all occurrances of OnAudioFilterRead cause Unity to freeze when hitting a breakpoint in an attached debugger
Steps to reproduce:
1. Open user attached project (AudioFilterBug)
2. Play the scene
3. Disable both "AudioSource" objects
4. Open "Main.cs" script
5. Attach a debugger
6. In the Update function set a breakpoint for the "++count;" line
7. Observe the frozen Unity editor even when the debugger is stopped
Expected result: All disabled objects with OnAudioFilterRead scripts assigned should not cause Unity to freeze when debugging
Reproduced in: 2017.2.0a4, 2017.1.0b10, 5.6.1p4, 5.6.0a5
Not reproduced in: 5.6.0a4, 5.5.2p3
Regression since: 5.6.0a5
Fixed in: 2017.2.0b6
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
Add comment