Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2019.4.X, 2020.1.X, 2020.2.X



Found in




Issue ID




Crash on mdb_txn_begin when SourceAssetDB has a lock on it from another process

Asset - Database


Steps to reproduce:
1. Create a new user or make sure you already have a secondary Windows user
2. Create a new project (possible to skip this if you already have one)
3. Navigate to the project's folder and open Library
4. Find SourceAssetDB file
5. Make it non-readable for the other Windows user (Right-click -> Properties -> Security -> Edit... -> Choose the other user -> Tick "Deny" or Read permission)
6. Log into the other user
7. Attempt to open the project

Reproducible with: 2019.3.0a1, 2019.3.0f6, 2020.1.0a21
Not reproducible with:2017.4.36f1, 2018.4.16f1, 2019.2.20f1

First lines of the stacktrace:
0x00007FF66E4E646F (Unity) mdb_txn_begin
0x00007FF66C2058C2 (Unity) LMDB_Transaction::Open
0x00007FF66C20255A (Unity) LMDB_Transaction::LMDB_Transaction
0x00007FF66C1B8324 (Unity) IsSourceAssetDBVersionCorrect
0x00007FF66C1E5452 (Unity) InitializeAssetDatabaseV2

- Versions deemed not reproducible doesn't have SourceAssetDB file in the Library at all
- Usually reproducible by the users when trying to open a project created on another Windows account while the initial account is completely logged off

  1. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0a4
    An error window was implemented, which informs that some of the processes are locked thus preventing Unity to open that specific project.

  2. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0b12

  3. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.14f1

  4. Resolution Note (fix version 2019.4):

    Fixed in: 2019.4.23f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.