Search Issue Tracker
Fixed
Votes
0
Found in
2023.2.1f1
Issue ID
UUM-56880
Regression
No
Crash on <lambda_7296f9b2fd7bf3c18e8139f1eb4c7fe3>::operator() when opening a project with a corrupted database
Reproduction steps:
1. Open the attached “repro-project“
2. Observe the crash
Reproducible with: 2023.1.0a4, 2023.2.1f1, 2023.3.0a11
Not reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.1.0a3, 2023.3.0a15
Fixed in: 2023.3.0a12
Reproduced on: Windows 10, Windows 11 (by reporter)
Not reproducible on: No other environment tested
Note: Opening with versions 2023.3.0a12, 2023.3.0a15 after experiencing the crash triggers a pop-up: “The Database Version could not be determined,“ indicating 'Library/SourceAssetDB' may be corrupted. Options given are to 'Re-create Database' (which opens the Editor) or 'Quit'
First few lines of the stack trace:
0x00007FFB08F9C371 (Unity) <lambda_7296f9b2fd7bf3c18e8139f1eb4c7fe3>::operator()
0x00007FFB09024757 (Unity) LMDB_Transaction::Run
0x00007FFB08FAA0A6 (Unity) DatabaseUpgrader::UpgradeDatabase
0x00007FFB08F6F53E (Unity) DBVersionUpgrade
0x00007FFB08F80553 (Unity) InitializeAssetDatabaseV2
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-41316