Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2020.2.0a10
Issue ID
1241280
Regression
No
Crash when performing step over
Crash when performing step over
1. What happened
Attempted to step over: await UniTask.DelayFrame(10); and the editor crashes due to an assert.
2. How we can reproduce it using the example you attached
Open attached project
Open test scene
Attach debugger and put breakpoint on line 14 :: val innerLol = 10;
Hit play in editor
Hit step over twice
observe crash
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2020.2):
Issue has been fixed in UniTask plugin and debugging will no longer crash. Mono debugger now will no longer assert and crash if it encounters a missing debug id for a generic. Several other asserts have also been removed.