Search Issue Tracker
Won't Fix
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.2.X, 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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
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.