Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.2.X, 2021.1.X
Votes
0
Found in
2019.4.14f1
2020.2.0a5
2021.1
Issue ID
1292368
Regression
Yes
Adding event handler to NetworkChange.NetworkAvailabilityChanged crashes the Linux Editor at "mono_dl_fallback_unregister"
How to reproduce:
1. Open the user attached project (Test.zip)
2. Enter and leave playmode several times until a crash occurs
Reproducible with: 2019.4.15f1, 2020.1.14f1, 2020.2.0a5, 2020.2.0b13, 2021.1.0a6
Not reproducible with: 2018.4.29f1, 2020.2.0a4
Notes:
1. Reproducible on Ubuntu 18.04
2. On Windows 10 a "PlatformNotSupportedException" is thrown
3. The build of the project doesn't crash
Comments (1)
-
RomainSepulchre
Feb 15, 2022 21:47
Hello, I have this issue on a windows 10 with Unity 2021.1.15f1. When I try to add an event to NetworkChange.NetworkAvailabilityChanged I have a "PlatformNotSupportedException" I also tried to upgrade my project to the last 2021.1 version (2021.1.28f1) but I still have the same issue. It happens everytime I try to add an event in editor and in a build
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2021.2):
Fixed issue where CreateNLSocket on posix systems would return an incorrect handle.
Fixed in 2021.2.0a2
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b5
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.20f1