Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.38f1
2021.3.9f1
2022.2.0b3
2023.1.0a8
Issue ID
UUM-12667
Regression
No
Crash on mono_traverse_object_internal when playing a scene
How to reproduce:
1. Open the user's attached project
2. Open scene "Scenes/Level"
3. Enter Play mode
Expected result: The Editor plays the scene
Actual result: The Editor crashes
Reproducible with: 2020.3.38f1, 2021.3.9f1, 2022.2.0b3, 2023.1.0a8
Reproduced on: Windows 10
Stacktrace:
0x00007ff90f7cdc51 (mono-2.0-bdwgc) [unity-liveness.c:379] mono_traverse_object_internal
0x00007ff90f7cdc16 (mono-2.0-bdwgc) [unity-liveness.c:367] mono_traverse_object_internal
0x00007ff90f7cdd17 (mono-2.0-bdwgc) [unity-liveness.c:478] mono_traverse_objects
0x00007ff90f7ce351 (mono-2.0-bdwgc) [unity-liveness.c:928] mono_unity_liveness_calculation_from_root
0x00007ff7b60146f2 (Unity) MarkDependencies
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The problem appears to come from code within a native dll that the user was using. They have notified us that they have corrected the problem in their code/project and are able to proceed.
Resolution Note (2023.1.X):
The problem appears to come from code within a native dll that the user was using. They have notified us that they have corrected the problem in their code/project and are able to proceed.