Search Issue Tracker
Fixed
Fixed in 2022.3.6f1, 2023.1.7f1, 2023.2.0a6
Votes
7
Found in
2022.2.0b10
2023.1.0a13
Issue ID
UUM-16091
Regression
No
Crash on ClothScene::PrepareScene when entering Play mode
Reproduction steps:
# Open the attached project “IN-18064.zip“
# Enter Play mode
Expected result: Play mode is entered successfully without the Editor crashing
Actual result: the Editor crashes
Reproducible with: 2022.2.0b10, 2023.1.0a13
Could not test with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1 - due to errors in the Console when downgrading the project
Reproduced on: Windows 10 Pro
First few lines of the stack trace:
{{0x00007ff6e7e140b9 (Unity) ClothScene::PrepareScene }}
{{0x00007ff6e7e13aae (Unity) ClothManager::LateUpdate }}
{{0x00007ff6e7e1309b (Unity) `ClothManager::Initialize'::`2'::PostLateUpdatePhysicsSkinnedClothBeginUpdateRegistrator::Forward }}
{{0x00007ff6e755c2da (Unity) ExecutePlayerLoop }}
{{0x00007ff6e755c463 (Unity) ExecutePlayerLoop}}
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Upita
Aug 03, 2023 04:01
2022.3.6f1 still cause crash :(
jura_wd
Jul 04, 2023 05:20
dear Unity people, what do you mean 'under consideration' for 2022.3.x? this is LTS - you must backport it!
tonym_lab42
Mar 21, 2023 09:23
We are seeing this 100% in our project on 2022.2.8 (after changing some unrelated items in our scene).
Would be nice to have this fix in a 2022.2.*