Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f2
Issue ID
928567
Regression
No
Coroutine is two times more expensive than Update method
Steps to reproduce:
1. Open user attached project (Unity_Test_Update_Calls)
2. Open profiler
3. Play the scene
4. Press the Update button in the scene
5. Press the Yield null button in the scene
6. Notice that the ms difference of "Yield null" is twice as big as the "Update" method
Expected result: Coroutines should not be slower than Update() calls.
Reproduced in: 2017.2.0b2, 2017.1.0f3, 5.6.2p2, 5.5.4p1, 5.4.5p4
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
Add comment