Search Issue Tracker
By Design
Votes
0
Found in
2017.3.1p4
Issue ID
1018883
Regression
No
Network error occurred: NoResources error is thrown when client stops calling NetworkTransport.Recieve
How to reproduce:
1. Open given Unity project
2. Enter "test" scene
3. Enter Play Mode
4. Wait 5 seconds and server crashes intentionally
5. Wait a little bit more and a lot of errors are thrown
Expected result: When server crashes it should stop sending messages
Actual result: When server crashed it still sends messages to the client
Reproducible with: 2018.2.0a5, 2018.1.0b12, 2017.4.0f1, 2017.3.2f1, 2017.2.2p2, 2017.1.3p2
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