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
- mono callstack overflow when callling Resources.UnloadUnusedAssets and c# scripts contain large, nested arrays
- Unloading an AssetBundle that contains a material causes a call to FindObjectsOfType
- GetObject failed to find Object for Library Representation is thrown when generating UV maps
- Editor crashes when compiling back thread function if it calls native plugins
- [Android] Changing the value of a slider, the volume does not change on a device
Add comment