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
- [URP] Searchable context menu instantly closes when attempting to open it
- [Multiplayer Center] Hosting Model Doesn't Reset to Recommended When Re-selecting Default Netcode Solution
- Clear Dynamic Data On Build does not clear data after a Clean Build when the Atlas Population Mode is set to "Dynamic" or "Dynamic OS"
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
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.