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
- Adaptive Probe Volumes Fails to Bake with Dilation Enabled and exception "Cannot allocate more brick chunks, probe volume brick pool is full" is printed
- AssertionException thrown and Mesh turns invisible when changing Material Offset manually via the Inspector or through SetTextureOffset() on a Mesh with more than one Material
- NavMesh is not usable when using empty Bounds in BuildNavMeshData
- A 404 page is opened when selecting "Open Documentation" for any SpeedTree Sub-graph Asset
- A 404 page is opened when selecting "Open Documentation" for any custom Sub-graph in Shader Graph
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.