Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.21f1
2023.3.0b10
6000.0.0b11
Issue ID
UUM-66069
Regression
Yes
Crash with multiple stack traces when opening a project with a corrupted database
Reproduction steps:
1. Open the attached “repro-project“
2. In the “Enter Safe Mode?“ pop-up select “Ignore“
3. Observe the crash
Reproducible with: 2022.3.21f1, 2023.2.7f1, 2023.3.0b10
Not reproducible with: 2021.3.36f1, 2023.2.13f1
Fixed in: 2023.2.8f1
Reproduced on: Windows 10, Windows 11 (by reporter)
Not reproducible on: No other environment tested
Notes:
1. The Editor does not crash when opening the project in Safe Mode
2. When opening the project with 2023.2.13f1, a “Fatal Error!” pop-up appears stating: “Database corruption detected. Please restart editor with '--rebuildLibrary' argument“
3. The project can be opened after deleting the library folder or after adding the '--rebuildLibrary' argument before opening it
4. Could not find the exact regression point due to the Editor crashing with stacktraces pointing to different issues
5. The “Fixed in” version shows the version where the “Fatal Error!“ pop-up started appearing
First few lines of the stacktraces:
0x00007ff7842bb4d7 (Unity) MonoScriptManager::InitializeRegisteredScripts
0x00007ff78575bc8b (Unity) RefreshInternalV2
0x00007ff785763dcc (Unity) StopAssetImportingV2Internal
0x00007ff7857526cd (Unity) InitialRefreshV2
0x00007ff784f62ac6 (Unity) Application::InitializeProject
0x00007FFADA11E107 (Unity) IsArtifactStillRelevant
0x00007FFADA11D6B0 (Unity) FindArtifactsToRemove
0x00007FFADA11DB6A (Unity) GarbageCollectArtifacts
0x00007FFADA07A0B6 (Unity) InitializeAssetDatabaseV2
0x00007FFADA03AB85 (Unity) AssetDatabase::InitializeAssetDatabase
0x00007ff761df0633 (Unity) ImportAsset
0x00007ff761e1449a (Unity) AssetImportWorker::Import
0x00007ff761e43fba (Unity) AssetImportManager::ImportInProcess
0x00007ff761e40f6d (Unity) AssetImportManager::Import
0x00007ff761e44bdf (Unity) ImportOutOfDateAssets
0x00007FF7081D1EF9 (Unity) CachedWriter::Write
0x00007FF7085917B1 (Unity) SerializedFile::FinishWriting
0x00007FF708583E60 (Unity) PersistentManager::WriteFile
0x00007FF70858529F (Unity) PersistentManager::WriteFile
0x00007FF7098C621A (Unity) WriteCachedMetaData
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
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
- Crash on Object::GetCachedScriptingObject when entering Play Mode
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.