Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
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:
1. Entering Play Mode
2. Opening a Scene
3. Importing Packages
4. Working with Materials
5. 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
Note: Not reproduced by CQA
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadow cascades and lights flicker when using Shadowmap Sampling
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
Add comment