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
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
- Overlays are focused when using the "Frame Selected in Window under Cursor" Shortcut just after Editing Overlay Fields
- Changes to Splash Screen in inactive Build Profile are not displayed in the Build Profile Splash Screen Preview
- [Package Manager] Vulkan Native Rendering Plugin can no longer intercept Vulkan Initialization, as it is loaded later when added via Package Manager
Add comment