Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.3.1
Issue ID
MTTB-595
Regression
No
Virtual machine crash on mdb_txn_begin when trying to enable Virtual Player
How to reproduce:
1. Open the attached “IN-86180“ project
2. Navigate to Window → Multiplayer → Multiplayer Play Mode
3. Check “Player 2“ to activate a virtual player
4. Observe the crash
Reproducible with: 1.2.2 (6000.0.5f1), 1.3.0 (6000.0.22f1), 1.3.1 (6000.0.23f1)
Reproduced on: Windows 10 (user), Windows 11
Not reproduced on: No other environment tested
Notes:
* Reported on GPU: NVIDIA GeForce RTX 4060 Ti, NVIDIA GeForce GTX 1660 Ti, NVIDIA GeForce RTX 3080
* Not reproduced by CQA
First few lines of the stack trace:
{noformat}0x00007FFF1BB1D68F (Unity) mdb_txn_begin
0x00007FFF1B31862F (Unity) LMDB_Transaction::Open
0x00007FFF1B315CCA (Unity) LMDB_Transaction::LMDB_Transaction
0x00007FFF1B2B0477 (Unity) SourceAssetDB::SourceAssetDB
0x00007FFF1B2759F6 (Unity) InitializeAssetDatabaseV2{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
- [Android] [GameActivity] UI is unresponsive when Application Entry Point is set to GameActivity
- [Linux] VR template "Tutorial Player" GameObject becomes blank after entering Play mode
- Editor window minimizes when changing the Layout while using the Windows split-screen function
- Object pools do not reset when re-entering the Play Mode with reload domain disabled
- Performance issue when using Shadow-Casting Lights with Batch Renderer Groups
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-87484