Search Issue Tracker

Fix In Review for 6000.6.0a1

Fix In Review for 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

Search

-

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

  1. Resolution Note (fix version 6000.6.0a1):

    Fixed in 6000.5.0a8

  2. Resolution Note (fix version 6000.5.0a8):

    Fixed in 6000.5.0a8

  3. Resolution Note (fix version 6000.4.0b11):

    Fixed in 6000.4.0b11

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues