Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
2020.1.14f1
2020.2.0b12
2021.1.0a4
2021.2.0a5
2021.2.0a7
Issue ID
1318561
Regression
No
Errors are thrown in the console after opening a project with a read-only SourceAssetDB file
How to reproduce:
1. Create a new Unity project
2. Go to the project folder
3. Go to Library -> "SourceAssetDB" and right-click on it
4. Open Properties and check "Read-only" and click on "Apply"
5. Open the project
6. When a popup appears click on "Force file writable"
7. When the project opens check to console
Expected results: There are no errors in the console
Actual results: There are 7 errors in the console
Reproducible with: 2020.1.14f1, 2020.1.17f1, 2020.2.0b12, 2020.2.7f1, 2021.1.0a4, 2021.1.0b10, 2021.2.0a7
Could not test: 2018.4.32f1 (Library doesn't contain the file) 2019.4.21f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a3 (popup feature wasn't implemented)
Note:
- There are six "Cannot open lmdb database Library/SourceAssetDB because another process has a lock on it. Will retry." errors and "mdb_env_open failed on 'Library/SourceAssetDB' with error: 5 'Input/output error'" error
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [MacOS] Invalid Code Signing Entitlements errors appear when signing MacOS project for App Store
- Missing UNITY_MATRIX_IT_MV definition in HDRP shaders
- ScrollRect panel not resizing correctly to fit text
- Scroll bar doesn't show full text
- [Linux] AutoLocale: current locale expects 'C' but got error is thrown when starting a project
Add comment