Search Issue Tracker
Fixed in 5.6.0
Votes
4
Found in
5.4.2p3
Issue ID
849219
Regression
No
Windows host server does not release connections when WebGL client disconnects, crashes on reaching max connections
Steps to reproduce:
1. Download the attached project**
2. Open the Windows build located in "case_849219-ReconnectTest\ReconnectTest\Builds"
3. Open the WebGL build located in "case_849219-ReconnectTest\ReconnectTest\Builds\WebGL" on a different machine
4. In the windows instance, press "Start Server"
5. In the WebGL instance, enter the Host's IP address in the text box
6. Click Connect
7. On the machine running the WebGL instance, open the "Network and Sharing Center"
8. Disable the internet adapter
9. Enable the internet adapter
10. Repeat steps 8-9
Result: Windows client crashes
**Optional steps:
1. Open the project
2. Build for Standalone
3. Build for WebGL
Reproduced on 5.2.3f1. 5.3.6p8, 5.4.2p3, 5.5.0b11
Notes:
1. Cannot connect from a windows build to windows, windows to webgl or webgl to windows
2. The windows instance can be run in the editor.
========== OUTPUTING STACK TRACE ==================
0x00000001416AFC7E (Unity) `anonymous namespace'::callback_unity_game
0x00000001417AE3DE (Unity) user_callback_handle_rxflow
0x00000001417AEF3F (Unity) lws_handle_POLLOUT_event
0x00000001417AF1FE (Unity) libwebsocket_service_fd
0x00000001417AF6B2 (Unity) lws_plat_service
0x0000000140CD0AFF (Unity) UNET::Reactor::Run
0x0000000140CD0E87 (Unity) UNET::Reactor::ThreadFunc
0x0000000140F8083C (Unity) Thread::RunThreadWrapper
0x00007FFACF0D8364 (KERNEL32) BaseThreadInitThunk
0x00007FFACF8F5E91 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========
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