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
Comments (2)
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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
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