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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.