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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Add comment