Search Issue Tracker
Fixed
Fixed in 6000.0.56f1, 6000.1.15f1, 6000.2.0b13, 6000.3.0a1
Won't Fix in 2022.3.X
Votes
1
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b12
6000.2.0a7
6000.3.0a1
7000.0.0a35
Issue ID
UUM-101784
Regression
No
Crash on PersistentManager::GetSerializedFileIfObjectAvailable when opening a specific project
Reproduction steps:
1. Open the attached project "CrashRepro"
Expected result: Project opens
Actual result: Project crashes and loading window does not close
Reproducible with: 2022.3.60f1, 6000.0.43f1, 6000.1.0b12, 6000.2.0a7
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
You can check if it has crashed in the Editor logs once the loading window shows “Open Project: Open Scene“, but it does not show up every time
First few lines of stack trace:
{noformat}0x00007FFFE07F45FC (Unity) PersistentManager::GetSerializedFileIfObjectAvailable
0x00007FFFE07FA6A5 (Unity) PersistentManager::ReadAndActivateObjectThreaded
0x00007FFFE07F80A1 (Unity) PersistentManager::LoadRemainingPreallocatedObjects
0x00007FFFE07F70D2 (Unity) PersistentManager::LoadFileCompletelyThreaded{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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Resolution Note (2022.3.X):
This crash has not been reported or observed on Unity 2022.3 directly; it can only be reproduced by opening up an already-corrupted Unity 6 project (where the crash has been resolved by now) in Unity 2022.3. Moreover, Unity 2022.3 support has expired except for Enterprise customers. As such, we are not considering to backport a fix.