Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.2p2
Issue ID
768846
Regression
Yes
[AssetImport] Importing FBX causes editor to run out of memory and crash
Steps to reproduce:
1. Create new project using Unity 5.1
2. Download attached FBX file and import it
3. Notice error in console that file is corrupt or invalid
4. Create new project using Unity 5.2+
5. Try importing same FBX
6. Notice popup window saying that Unity is out of memory and has to be closed
Not reproducible: 5.1.4f1
Reproduced with: 5.2.4p1, 5.3.2p2, 5.4.0b5
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
gwendalbroudin
Oct 04, 2016 15:39
Same as @DADUMMY in Unity 5.4.1f1 on windows
DaDummy
Oct 02, 2016 16:23
I can still reproduce this issue in Unity 5.4.1f1 on Linux