Search Issue Tracker
Third Party Issue
Votes
4
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
Issue ID
UUM-92221
Regression
No
Crash on RaiseException during Socket.BeginConnect in Player when application connection is blocked through commercial firewall
How to reproduce:
1. Download and install ZoneAlarm Pro + Firewall (possibility of 30 day free trial)
2. Open the attached “IN-91171.zip” project
3. Build and run the application
4. Close the application once it has loaded
5. Open ZoneAlarm
6. Under Application Permissions, find the built application, set the action to “Block Connection” and hit Save
7. Run the built application again
8. Observe the crash
Reproducible in: 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}0x00007FFCD9C2837A (KERNELBASE) RaiseException
0x00007FFBF3060C1C (mono-2.0-bdwgc) mono_dl_fallback_unregister
0x00007FFBF304C822 (mono-2.0-bdwgc) BrotliEncoderVersion
0x00007FFBF304C888 (mono-2.0-bdwgc) BrotliEncoderVersion
0x00007FFBF32070BB (mono-2.0-bdwgc) mono_thread_has_sufficient_execution_stack{noformat}
Notes:
- Only reproducible in build
- Issue is not specific to ZoneAlarm firewall
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This is a duplicate of a known issue: https://issuetracker.unity3d.com/issues/crash-on-system-dot-net-dot-sockets-dot-socket-queueioselectorjob-when-using-a-vpn-and-opening-a-project-that-uses-visual-studio
As part of mono's initialization of its threadpool it establishes a socket connection to itself on localhost. Some firewalls (and VPNs) are very aggressive and block access to any socket API call by a process, even if it is not an outbound connection. Fixing this issue would require a large rewrite of mono's threadpool implementation which is too risky of a change at this time.