Search Issue Tracker
Fixed
Fixed in 6000.2.13f1, 6000.3.0b11, 6000.4.0a5, 6000.5.0a2
Votes
0
Found in
6000.2.11f1
6000.3.0b9
6000.4.0a4
6000.5.0a1
Issue ID
UUM-125809
Regression
Yes
Crash on UnityYAML::Read::ParsePlainScalar when opening a specific project
How to reproduce:
1. Open the attached “IN-123034” project
2. Observe the crash
Reproducible with: 6000.2.0a4, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4
Not reproducible with: 6000.0.62f1, 6000.2.0a3
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note: The crash still reproduces after deleting the Library folder
First few lines of the stack trace:
0x00007FFDC577E191 (Unity) UnityYAML::Read::ParsePlainScalar
0x00007FFDC577DBCD (Unity) UnityYAML::Read::ParseNode
0x00007FFDC577BAA7 (Unity) UnityYAML::Read::Parse
0x00007FFDC57B6337 (Unity) MetaFileHandling::MetaFileAccessor::TryCreate
0x00007FFDC57F60A8 (Unity) FileHasher::ComputeFileHashJob
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment