Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.1p1
Issue ID
1003117
Regression
Yes
SocketException: ConnectionReset is thrown while transferring data under .net 4.6
Steps to reproduce:
1. Open the attached project (OC)
2. Build a standalone build
3. Open one instance of Unity Player
4. Open a second instance of Unity Player
5. Enter a username for the Host
6. Click Play on the Host
7. Wait for Host to finish connecting and for the scene to load
8. Enter a username for the Client
9. Wait for the Client to finish connecting
10. Press “Space” once to trigger the data transfer on the Host
11. Debug errors will be displayed on the Host and Client to show the flow of information:
Receiving failed. SocketException: ConnectionReset
Actual results: SocketException: ConnectionReset is thrown while transferring data
Expected results: Should successfully transfer the data
Note:
Unable to reproduce with 2018.1.0b12 and 2018.2.0a6 due to another bug
Not 100% reproducible
Decreasing the maxBytesPerChunk fixes the issue
Reproduced with: 2017.1.1p3, 2017.1.3p2, 2017.2.2p2, 2017.3.2f1
Not reproduced with: 2017.1.1p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Add comment