Search Issue Tracker
Fixed in 6000.6.0a1
Fixed in 6000.4.0b11, 6000.5.0a8
Under Consideration for 6000.3.X, 6000.5.X, 6000.6.X
Votes
2
Found in
6000.4.0b4
6000.5.0a4
Issue ID
UUM-133590
Regression
No
Crash on ReadWriteLock::WriteLock when performing various Unity operations
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
- Importing Packages
- Working with Materials
- Opening Visual Studio
Reproducible with versions: 6000.3.0a5-6000.3.6f1, 6000.4.0a2-6000.4.0b4, 6000.5.0a3-6000.5.0a4 (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:
0x00007FFBDD7BA669 (Unity) ReadWriteLock::WriteLock
0x00007FFBE03747BC (Unity) LMDB_Database::IncreaseDatabaseSize
0x00007FFBE049B713 (Unity) LMDBIndexStorage::MergeArtifactsBatch
0x00007FFBE049B59F (Unity) LMDBIndexStorageBindings::MergeArtifacts
0x00007FFBE04A30E4 (Unity) LMDBIndexStorage_CUSTOM_Internal_MergeArtifacts
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
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b11):
Fixed in 6000.4.0b11