Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2020.1.0a19
2020.2
2020.3
2020.3.1f1
Issue ID
1378177
Regression
Yes
Unity crashes on block_merge_next when importing an FBX file
Reproduction steps:
1. Create a new Unity project
2. Drag "1378177-sample.fbx" or "1378177-sample-2.fbx" file into the project
Expected result: Files are imported
Actual result: Editor crashes
Reproducible with: 2020.1.0a19, 2020.1.0a24, 2020.2.7f1, 2020.3.9f1
Not reproducible with: 2019.4.32f1, 2020.1.0a18, 2020.3.10f1, 2020.3.23f1, 2021.2.3f1, 2022.1.0a15
First lines of the stacktrace:
0 com.unity3d.UnityEditor5.x 0x000000010bca9a50 block_merge_next + 128
1 com.unity3d.UnityEditor5.x 0x000000010bca992f tlsf_free + 287
2 com.unity3d.UnityEditor5.x 0x000000010824ba71 DynamicHeapAllocator::Deallocate(void) + 529
3 com.unity3d.UnityEditor5.x 0x000000010823509b DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate(void) + 139
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Resolution Note (fix version 2020.3):
Fixed in 2020.3.10f1