Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.14f1
2022.1.23f1
2022.2.0a8
Issue ID
UUM-20084
Regression
Yes
Crash on mdb_cursor_next when opening a project with a corrupted file
Reproduction steps:
1. Open the attached “repro-project”
Expected result: The project opens successfully
Actual result: The Editor crashes
Reproducible with: 2021.2.0a17, 2021.3.14f1, 2022.1.23f1, 2022.2.0a8
Not reproducible with: 2020.3.42f1, 2021.2.0a16, 2022.2.0a9, 2022.2.0b15, 2023.1.0a18
Reproduced on: Windows 10 Pro
Note: Not reproducible in a newly created project
First few lines of the stack trace:
0x00007ff79cab4999 (Unity) mdb_cursor_next
0x00007ff79cab4499 (Unity) mdb_cursor_get
0x00007ff79c35250f (Unity) LMDB_Enumerator::Next
0x00007ff79c2dbc48 (Unity) SourceAssetDBReadTxn::GetAllGUIDs
0x00007ff79c31cbb3 (Unity) RefreshInternalV2
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
The test project provided is corrupted besides the db itself. For example:
\Assets\TextMesh Pro\Examples & Extras\Scripts\TextConsoleSimulator.cs
is corrupt.