Search Issue Tracker
Fixed in 2019.2
Fixed in 2018.4, 2019.1
Votes
2
Found in
2018.3.0b2
2019.1.1f1
Issue ID
1153078
Regression
Yes
Debugging Unity C# code containing Async/Await breaks debugger & causes Editor to hard crash
How to reproduce:
1. Open attached project "case_662397-asyncCrashRepro.zip" and scene "AsyncRepro"
2. Open Visual Studio and attach the Unity Editor for debugging
3. In Visual Studio, place a breakpoint on line 62 (on int b = 0)
4. In Unity Editor, enter Play mode
5. In Visual Studio, press "Step Out" button (shortcut is Shift + F11)
6. Observe Unity Editor
Expected result: the Editor runs smoothly
Actual result: the Editor crashes
Reproducible with: 2018.3.14f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0b2, 2019.3.0a2
Not reproducible with: 2017.4.27f1, 2018.2.21f1
Could not test with: 2018.3.0a1, 2018.3.0b1 (Visual Studio does not find coresponding location, image attached)
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
- [Build Callbacks] Build is not failing when BuildFailedException is thrown in the PostProcessScene Callback
- [Terrain] The function TerrainData.GetDetailLayer only returns 0 or 1
- [Windows 7] VideoPlayer.Prepare causes a stack overflow crash if Video is loaded from asset bundle
- [WebGL] Mouse input is blocked after a few moves when using Edge browser
- Builds that contain terrain using the Nature/Terrain/Standard shader produce errors when run in headless mode
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0b7, 2019.3.0a7