Search Issue Tracker
Fixed
Fixed in 6000.2.0a10
Votes
0
Found in
6000.2.0a9
Issue ID
UUM-119588
Regression
Yes
Crash on SerializedFile::IndexTextFile when importing specific assets
How to reproduce:
1. Create a new project
2. Drag and drop into /Assets the custom package: “IN-112289_ModelBug.unitypackage”
3. When prompted to import the package, click “Import”
4. Observe the crash
Reproducible with: 6000.2.0a8 (8a36f491c000), 6000.2.0a9
Not reproducible with: 6000.0.57f1, 6000.2.0a7, 6000.2.3f1, 6000.3.0b1 (fcdf07aae9b4)
Fixed in: 6000.2.0a10
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of the crash:
0x00007FFE4981FCA8 (Unity) SerializedFile::IndexTextFile
0x00007FFE4982102D (Unity) SerializedFile::InitializeRead
0x00007FFE49805210 (Unity) PersistentManager::GetStreamNameSpaceInternal
0x00007FFE49803479 (Unity) PersistentManager::GetAllFileIDs
0x00007FFE49803DB0 (Unity) PersistentManager::GetInstanceIDsAtPath
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment