Search Issue Tracker
Active
Votes
1
Found in
2019.4
2020.3
2020.3.11f1
2021.1
2021.2
2022.1
Issue ID
1346592
Regression
No
[Networking][IL2CPP] Socket.Close(0) in IL2CPP builds freezes the client if server can't be reached
Reproduction steps:
1. Open the attached user's project "Photon-Pun2-Deploy.zip"
2. Block port 5058 in the Firewall or a network tool
3. Open the Scene "MinimalConnect" and Build and Run it as Standalone IL2CPP build
4. When the client runs, give it maybe a second to try to connect, then click the "Disconnect" button
5. Open the Profiler, you can see the spike of one second and explore into the place where it is (Check attached Profiler.png)
Expected result: As the protocol is not connection-oriented, a connection close without delay is expected
Actual result: If the connection is blocked and the user / logic calls Socket.Close() (or Socket.Close(0)) at that moment, this results in a 1 second blocking operation deeper in Socket.Dispose()
Reproduces on: 2019.4.30f1, 2020.3.22f1, 2021.1.18f1, 2021.2.0b12, 2022.1.0a9
Notes:
-The issue is NOT present when using Socket.Send and Socket.BeginReceive
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment