Search Issue Tracker
Fixed in 2017.1.X
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
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Add comment