Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.9f1
2023.1.12f1
Issue ID
UUM-48376
Regression
No
Crash on CollectAllSceneObjectRoots when exiting the 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 steps 2-3 until Editor crashes
Expected result: Domain is reloaded
Actual result: Editor crashes
Reproducible with: 2022.3.9f1, 2023.1.12f1, 2023.2.0a13
Not reproducible with: 2023.3.0a4
Couldn’t test with: 2021.3.30f1 - “error CS0234: The type or namespace name 'Properties' does not exist in the namespace 'Unity' (are you missing an assembly reference?)“
Fixed in: 2023.2.0a14
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note: Reproduction rate is below 5%
First few lines of stack trace:
{noformat}0x00007ff774c640f4 (Unity) CollectAllSceneObjectRoots
0x00007ff775f34783 (Unity) EditorSceneManager::RestoreSceneBackups
0x00007ff775c3268f (Unity) PlayerLoopController::ExitPlayMode
0x00007ff775c427c0 (Unity) PlayerLoopController::SetIsPlaying
0x00007ff775c45e40 (Unity) Application::TickTimer
0x00007ff7760b9cda (Unity) MainMessageLoop{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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
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.