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
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
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.