Search Issue Tracker
By Design
Votes
0
Found in
2018.2.2f1
2018.2.5f1
Issue ID
1079673
Regression
Yes
Network Manager has increased cpu usage in linux player after upgrade to 2018.2
To reproduce:
1) Open attached project
2) Build for Linux
3) Run it and check CPU usage in the monitor or another app
Expected: 0%
Actual: 4%
Reproduced in 2018.2.2f1, 2018.2.3f1, 2018.2.5f1, 2018.2.12f1, 2018.3.0b5
Not reproduced in 2018.2.1f1, 2018.2.0f2, 2018.1.6f1
Not reproduced in Win 10 (identical usage across versions)
Prior to 2018.2.2f1, there was a bug that limited headless server frame rate to 60fps. This was corrected in 2018.2.2f1, allowing headless servers to run at unlimited framerates. Running at a high or unlimited framerate will burn more CPU. Headless servers should set Application.targetFrameRate; see https://docs.unity3d.com/ScriptReference/Application-targetFrameRate.html
Setting Application.targetFrameRate = 60 results in the lower cpu usage observed prior to 2018.2.2f1.
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
Resolution Note (2019.1.X):
Prior to 2018.2.2f1, there was a bug that limited headless server frame rate to 60fps. This was corrected in 2018.2.2f1, allowing headless servers to run at unlimited framerates. Running at a high or unlimited framerate will burn more CPU. Headless servers should set Application.targetFrameRate; see https://docs.unity3d.com/ScriptReference/Application-targetFrameRate.html
Setting Application.targetFrameRate = 60 results in the lower cpu usage observed prior to 2018.2.2f1.