Search Issue Tracker
Won't Fix
Votes
4
Found in
5.6.0p3
Issue ID
908025
Regression
Yes
[UNET] CPU usage on 'LAN host' in 5.6 and 2017.1 versions is higher than in 5.5 or 5.4
To reproduce:
1. Open project on any Unity 5.5
2. Open activity monitor
3. Play 'Main' scene
4. Press 'H'
5. Repeat steps with the 5.6.0a5 version or higher.
Expected: CPU usage growth will be the same on all versions
Actual: CPU usage on 5.6 or 2017.1.0 will be twice higher
Reproduced on: 5.6.0a5, 5.6.0p3, 2017.1.0b2
Not reproducible on: 5.4, 5.5, 5.6.0a1, 5.6.0a3
Note:
NetworkManagerHUD.OnGUI(), NetworkIdentity.UnetStaticUpdate() and Network.Update shows simmilar results in profiler for all versions
Tested on:
OSX 10.12.4
2,8 GHz Intel Core i5
Intel Iris Pro Graphics 6200 1536 MB
-
LoadingHome
Sep 22, 2017 18:56
I reported this problem in early May, although here it says it's fixed is not so. I begin to think that they will never fix it. I miss the stability of unity 4.
-
matbou
Sep 05, 2017 12:55
Still waiting for the fix too
-
LoadingHome
Jun 02, 2017 17:10
The fix is still not present in the 2017.1b8 version or in any of the 5.6 patches. Is there any estimated time to implement the fix?
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
- 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
Resolution Note (2018.1.X):
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.