Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

2021.3.46f1

2022.3.53f1

6000.0.28f1

6000.1.0a5

6000.2.0a1

6000.3.0a1

6000.4.0a1

6000.5.0a1

Issue ID

UUM-88906

Regression

No

Crash with multiple stack traces when importing corrupted asset

Serialization

-

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

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.5.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.