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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment