Search Issue Tracker
Active
Under Consideration for 6000.3.X, 6000.4.X, 6000.5.X, 6000.6.X
Votes
0
Found in
6000.3.14f1
6000.4.5f1
6000.5.0b3
6000.6.0a5
Issue ID
UUM-141720
Regression
No
Crash on mdb_cursor_sibling when performing various actions in the Editor
A recurring crash issue in the Unity Editor has been observed, affecting various workflows. These crashes have been reported to happen when:
- Entering Play Mode
- Opening a Scene
- Creating/editing scripts
- Reloading domain
- Creating projects
- Opening Visual Studio
Reproducible with versions: 6000.3.0b1-6000.3.14f1, 6000.4.0a5-6000.4.5f1, 6000.5.0a3-6000.5.0b4 (Sentry data)
Reproducible on: Windows 10, Windows 11
Notes:
- Not reproduced by CQA
- Sentry only collects data for Windows crashes, so we are not able to determine if the issue is reproducible on other environments
First few lines of StackTrace:
0x00007FF83F42D99D (Unity) mdb_cursor_sibling
0x00007FF83F42D15C (Unity) mdb_cursor_prev
0x00007FF83F42C92E (Unity) mdb_cursor_get
0x00007FF83F137032 (Unity) LMDB_Enumerator::Next
0x00007FF83F3098F9 (Unity) LMDBIndexStorage::RemoveDocuments
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on Scripting::ScriptingWrapperFor when exiting Play Mode during an active web request
- Material Inspector shortly disappears resulting in "Add Component" button jumping when the Material is recompiled
- Hand Interaction Profile breaks hand teleport to arbitrary locations
- Grabbing Dynamic Attach interactable in Interaction Simulator makes controller spin
- XRI Starter Assets Interactable shader generates Console warnings
Add comment