Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2021.3.46f1
2022.3.53f1
6000.0.28f1
6000.1.0a5
Issue ID
UUM-88906
Regression
No
Crash with multiple stack traces when importing corrupted asset
Reproduction steps:
1. Open the attached “IN-89021.zip” project
2. Observe the crash or continue
3. Reimport “Pixel.asset”, located under Assets/General/
4. Observe the crash
Reproducible in: 2021.3.46f1, 2022.3.53f1, 6000.0.28f1, 6000.1.0a5
Reproducible on: MacOS 14.5 (M1), Windows 11
First few lines of stacktraces:
{noformat}0x00007FFF83EA33F9 (Unity) ContainerClear<std::map<DeprecatedFastPropertyNameSerialization,float,std::less<DeprecatedFastPropertyNameSerialization>,std::allocator<std::pair<DeprecatedFastPropertyNameSerialization const ,float> > > >
0x00007FFF83EBFE00 (Unity) UnityPropertySheet::Clear
0x00007FFF83E9A935 (Unity) Material::ResetWithShader
0x00007FFF8420063B (Unity) SerializedFile::ReadObject
0x00007FFF84200126 (Unity) SerializedFile::ReadObject{noformat}
{noformat}0x00007FFF1D7BC4F8 (Unity) BucketAllocator::Allocate
0x00007FFF1D7B2C08 (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007FFF1D7A42BD (Unity) MemoryManager::Allocate
0x00007FFF1D7AEC6E (Unity) malloc_internal
0x00007FFF1D202353 (Unity) core::vector<core::pair<int,int,0>,core::allocator<core::pair<int,int,0>,0> >::resize_buffer_nocheck{noformat}
Note: Sometimes, instead of crashing, the Asset Importing process is stuck and continues indefinitely
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
Add comment