Search Issue Tracker
Fixed in 2021.3.14f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a15
Votes
0
Found in
2021.3.9f1
2022.1.14f1
2022.2.0b5
2023.1.0a6
Issue ID
UUM-13031
Regression
No
Crash on mono_traverse_objects when using AppDomain.Unload and trying to load dll file
Reproduction steps:
1. Open the user's attached project
2. Open the "Main" Scene
3. Enter Play Mode
4. Press 'Q' when the scene fully loads
5. Wait for a few seconds until IOException is thrown in the Console
6. Exit Play Mode
Expected result: Play Mode is exited successfully
Actual result: The Editor crashes
Reproducible with: 2021.3.9f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a6
Reproducible on: Windows 11
Notes:
- may take a few times for the crash to reproduce
- 'IOException: Win32 IO returned 1224.' is thrown after pressing the 'Q' button on keyboard
First lines of stacktrace:
0x00007ffcb8a52af1 (mono-2.0-bdwgc) \[unity-liveness.c:482] mono_traverse_objects
0x00007ffcb8a52af1 (mono-2.0-bdwgc) \[unity-liveness.c:482] mono_traverse_objects
0x00007ffcb8a52b3a (mono-2.0-bdwgc) \[unity-liveness.c:482] mono_traverse_objects
0x00007ffcb8a53b01 (mono-2.0-bdwgc) \[unity-liveness.c:684] mono_unity_liveness_calculation_from_statics
0x00007ff6f34fad00 (Unity) GarbageCollectSharedAssets
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0a15
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b11
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.14f1