Search Issue Tracker
Fixed in 2023.1.0b5
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
1
Found in
2020.3.43f1
2021.3.16f1
2022.2.1f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21346
Regression
No
Crash on UnityYAML::Document::GetValueForKey when initializing the Application.AssetDatabase Refresh
Reproduction steps:
1. Open the attached “repro“ project
Expected result: The project opens successfully
Actual result: The Editor crashes (2023.1.0a23). The Editor hangs on Initial Asset Database Refresh (2020.3.43f1, 2021.3.16f1, 2022.2.1f1)
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.1f1, 2023.1.0a23
Reproduced on: Windows 10 Pro
First few lines of the stack trace:
{{0x00007FF96E44EFC0 (Unity) UnityYAML::Document::GetValueForKey }}
{{0x00007FF96E472BE3 (Unity) MetaFileHandling::ExtractPropertiesFromYAMLDocument }}
{{0x00007FF96E474A2B (Unity) MetaFileHandling::MetaFileAccessorWithProperties::GetProperties }}
{{0x00007FF96E4C52E5 (Unity) FileHasher::Hasher }}
{{0x00007FF96CF49E7D (Unity) Thread::RunThreadWrapper}}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment