Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.3
2019.3.2f1
2020.1
2020.2
Issue ID
1229786
Regression
No
Crash on DualThreadAllocator<DynamicHeapAllocator>::Allocate when importing a large .fbx file
How to reproduce:
1. Open the attached project "Case_1229786"
2. In the Project window select the "Canyon.fbx" file and reimport it
Reproducible with: 2017.4.39f1, 2018.4.21f1, 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
First lines of the stack trace:
0x00007ff6d1b3c2ea (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007ff6d1b23556 (Unity) MemoryManager::Allocate
0x00007ff6d1b29ffe (Unity) MemoryManager::Reallocate
0x00007ff6d1b38d38 (Unity) realloc_internal
0x00007ff6d3edafb2 (Unity) FBXRealloc
0x00007ffe92a3a62d (libfbxsdk) fbxsdk::FbxRealloc
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2021.1.X):
The system is running out of memory, the supplied "Canyon.fbx" file has 400-million polygons - it would not be our recommendation to run this on any kind of system.
We similarly have problems opening it in all major DCC tools.