Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
2
Found in
2022.3.56f1
6000.0.34f1
6000.1.0b1
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-92511
Regression
No
Crash on mono_traverse_object_internal when exiting Play mode on a specific project
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Enter the Play mode
3. Exit the Play mode
4. Repeat from step 2
Expected result: Play mode starts/stops
Actual result: Editor crashes
Reproducible with: 2022.3.56f1, 6000.0.34f1, 6000.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes: It usually takes about 20 times to enter/exit Playmode to crash. Crash on 6000.1.0b1 took significantly more attempts
First few lines of stack trace:
{noformat}
0x00007FFE1175A5B2 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\unity-liveness.c:388] mono_traverse_object_internal
0x00007FFE1175AE42 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\unity-liveness.c:484] mono_traverse_objects
0x00007FFE1175BD14 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\unity-liveness.c:814] mono_unity_liveness_calculation_from_root
0x00007FF74F010E4E (Unity) ProcessMonoBehaviour
0x00007FF74F00ECF4 (Unity) MarkDependencies
0x00007FF74F00E82F (Unity) MarkAllDependencies{noformat}
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.