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
- UI Image Position doesn't updated in Editor IF the object is not active while using PointerEventData eventData
- Linear Color Space cause Icons to become darker in Project Window then Terrain texture is set
- "The referenced script on this Behaviour is missing!" warning duplicates during recompile in Play mode with a Canvas selected
- Physics2d Boxcast distance is less than it should be
- RSQRTE(1.0f) on AMD cpu doesn't yeild 1.0f
Add comment