Search Issue Tracker
Fixed
Fixed in 6000.0.29f1, 6000.1.0a6, 7000.0.0a10
Votes
1
Found in
6000.0.26f1
6000.1.0a6
7000.0.0a10
Issue ID
UUM-87484
Regression
No
Crash on mdb_txn_begin when activating any of the Virtual Players
Prerequisites:
- enable "Load Previous Project on Startup" option in Unity > Settings > General
Steps to reproduce:
1. Open the “user's attached project”
2. Open “SampleScene”
3. Go to “Window/Multiplayer/Multiplayer Play Mode”
4. Select any of the Virtual Players through the “Multiplayer Play Mode” Window
5. Observe the crash
Reproducible with versions: 1.2.2, 1.3.0-pre.2 (6000.0.16f1)
Reproducible on: Windows 11 (by the reporter), MacOS
Not reproducible on: no other environment tested
First few lines of StackTrace:
{noformat}
0x00007FFF65B1D68F (Unity) mdb_txn_begin
0x00007FFF6531862F (Unity) LMDB_Transaction::Open
0x00007FFF65315CCA (Unity) LMDB_Transaction::LMDB_Transaction
0x00007FFF652B0477 (Unity) SourceAssetDB::SourceAssetDB
0x00007FFF652759F6 (Unity) InitializeAssetDatabaseV2{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment