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
- Grid lines displayed over game objects in the Scene view when SSAO is enabled
- [MacOS] Unity Render Pipeline NullReferenceException errors appear when building standalone
- Terrain's grass is rendered with a different shader than in the Editor when using Asset Bundles in Standalone build
- C# file opens in a new VS Code window when a VS Code Workspace is already open
- [TMP][Examples & Extras] Scene 24 shaders broken
Add comment