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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment