Search Issue Tracker

Won't Fix



Found in






Issue ID




Crash on mdb_cursor_put when a project in a Google Drive File Stream is opened using Asset Import Pipeline V2

Asset - Database


Reproduction steps:
1. Set up Google Drive File Stream (Instructions:
2. In the Google Drive File Stream create a project which uses Asset Import Pipeline V2 and attempt to open it

Reproducible with: 2019.2.0a5, 2019.2.21f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Not reproducible with: 2019.2.0a4 (Asset Import Pipeline V2 unavailable)
Didn't test with older versions as the crash seems to reproduce only when the project is being opened using Asset Import Pipeline V2

First lines of the stacktrace:
0x00007FF6D205699D (Unity) mdb_cursor_put
0x00007FF6D205E718 (Unity) mdb_put
0x00007FF6D0E809A9 (Unity) LMDB_Map::Set
0x00007FF6D0EE756F (Unity) SourceAssetDBWriteTxn::SetRootFolderProperties
0x00007FF6D0ED145C (Unity) `SourceAssetScanner::Refresh'::`2'::<lambda_1>::operator()

- With older versions, which don't use Asset Import Pipeline V2 by default, the bug is reproducible by going to Edit -> Project Settings -> Editor -> Asset Pipeline and choosing Asset Import Pipeline V2 to be used for the project
- The crash seems to affect not only Google Drive File Stream, but similar other services, as well as OneDrive and VMs using HGFS Network Drives
- Some users report that they cannot create and open new projects in these same locations due to this crash, but we're unable to reproduce that behaviour

  1. Resolution Note (2020.2.X):

    Unity requires the use of memory-mapped files to work correctly, which in some operating systems doesn't work well or at all over network shares; due to that, opening projects from network shares is not supported.

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.