Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.19f1
2023.1.0b16
2023.2.0a14
2023.3.0a3
Issue ID
UUM-35840
Regression
No
Crash on LMDB_Transaction::GetDatabase() when opening a specific project
Reproduction steps:
1. Open the attached "ASDQWE" project
Expected result: The Editor is opened
Actual result: The Editor crashes while loading
Reproducible with: 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Could not test with: 2020.3.48f1, 2021.3.25f1 (“Entities Graphics”, “Netcode for Entities” packages are not available for this version)
Reproducible on: Intel MacOS 13.3.1
First few lines of Stack trace:
{noformat}#0 0x00000104312e04 in LMDB_Transaction::GetDatabase()
#1 0x00000104274486 in SourceAssetDBReadTxn::SourceAssetDBReadTxn()
#2 0x000001042adb74 in GetAssetFolderInfoV2(core::basic_string_ref<char>, bool&, bool&)
#3 0x0000010420ab24 in AssetDatabase::GetAssetFolderInfo(core::basic_string_ref<char>, bool&, bool&){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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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.
Resolution Note (2023.3.X):
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.