Search Issue Tracker
Fixed
Fixed in 6000.0.32f1, 6000.1.0a9
Votes
0
Found in
6000.0.28f1
6000.1.0a5
Issue ID
UUM-90217
Regression
Yes
Crash on GetSpriteAtlasDependenciesFromBinary when opening specific project
Reproduction steps:
1. Open the attached “TestUnity6.zip” project
2. Observe the crash
Reproducible in: 2023.1.0b2. 6000.0.28f1, 6000.1.0a5
Not reproducible in: 2021.3.46f1, 2022.3.53f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stack trace:
{noformat}0x00007FF82F096694 (Unity) GetSpriteAtlasDependenciesFromBinary
0x00007FF82F09620F (Unity) SpriteAtlasImporter::GetSpriteAtlasDependencies
0x00007FF82F8C7E54 (Unity) AssetDatabase::ImportDependencyGetter::operator()
0x00007FF82F915870 (Unity) CalculateDependenciesOfOutOfDateAssets
0x00007FF82F91AA30 (Unity) AssetImportManager::Import{noformat}
Note: The reproduction becomes highly inconsistent below 2023.1.0b2 which makes finding the FAV nearly impossible due to the issue stopping/starting to reproduce on newer versions after upgrading or downgrading. For example, downgrade project to 2023.1.0b1 (no repro) → upgrade to 2023.1.15f1 (repro) → downgrade to 2023.1.0b1 (repro).
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 6000.1.0a9):
Fix case crash on GetSpriteAtlasDependenciesFromBinary when opening SpriteAtlas
Resolution Note (fix version 6000.0.32f1):
Fix case crash on GetSpriteAtlasDependenciesFromBinary when opening specific project