Search Issue Tracker
Fixed in Unity 2017.1
Votes
1
Found in
5.6.0b10
Issue ID
895273
Regression
Yes
Registering a handler with NetworkServer causes high CPU usage (caused by network thread starting)
Steps to reproduce:
1. Open attached project
2. Build & Run the scene
3. Open task manager and observe the huge CPU usage
Expected result: NetworkServer.RegisterHandler(MsgType.Highest + 1, FakeHandler) should not cause a CPU leak
Reproduced in: 5.6.0f2, 2017.1.0a4
Not reproduced in 5.5.1f1
Verified with 2017.1.0b6 version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Daydream] Changing volume at the same moment as RenderScale is being changed causes flickering or black view
- [VR] Google VR SDK for Unity asks to enable VR Support but proceeds to build anyway
- [VR]Changing renderViewportScale results in reduction of viewing space for the right eye when using Post Effects
- Plugin's "Platform Settings" value in Inspector is different compared to the meta file
- [Android] Video Player fails to play when application is built with Gradle Build System
Add comment