Search Issue Tracker
Fixed in 5.3.6
Votes
2
Found in
5.4.0b13
Issue ID
784481
Regression
No
Coroutines generate garbage in MoveNext
Coroutine::MoveNext causes the return value (a bool) to be boxed, which causes an allocation.
Reproduction Steps:
1. Run the attached project
2. Open the Profiler and sort by GC Alloc
3. Observe that FlagEndOfFrame is allocated 17B of garbage every frame
Expected Result:
It should be possible to run a coroutine without generating any garbage at all.
Comments (2)
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
jalf
Aug 22, 2017 04:04
It´s really fixed?!
Dino Dini
Mar 31, 2016 21:59
Also seen in 5.3.4f1. For any project using a lot of coroutines, this is a lot of garbage.