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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
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