Search Issue Tracker
Fixed
Votes
1
Found in
2022.3.17f1
Issue ID
UUM-60619
Regression
Yes
Crash on core::StringStorageDefault<char>::assign when opening a specific project
Reproduction steps:
1. Open the attached "crash_IN-64297" project
2. Observe the crash
Reproduced with: 2022.2.0a15, 2022.3.17f1
Not reproduced with: 2021.3.34f1, 2022.2.0a14
Couldn't test with: 2023.2.6f1, 2023.3.0b3 - the project is stuck on the loading screen and the logs show an infinite loop in the importing process
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Note: The crash on the FAV version is not reproducible on all devices. However, it doesn't seem to have neither a hardware pattern nor a software one
First few lines of the stack trace:
0x00007ff605f5251b (Unity) core::StringStorageDefault<char>::assign
0x00007ff60816626b (Unity) GuidDB::ProcessBlock
0x00007ff608164c0e (Unity) GuidDB::Process
0x00007ff608167ecc (Unity) SourceAssetDBWriteTxn::RefreshStage3_SyncDatabase
0x00007ff6081dd24e (Unity) <lambda_72d4138e75637852f4266ed91400ed85>::operator()
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14959