Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.3.1p4
Issue ID
1013071
Regression
No
Crash accessing uninitialized memory when importing FBX with animated user properties and multiple clips
How to reproduce:
1. Create a new project
2. Copy the attached fbx file onto the Assets folder of your project.
3. Select the FBX asset in Unity, go to the animation tab on the Inspector Window.
4. Click on the "Animated Custom Properties" checkbox
5. Click "Apply" button
Actual result: The crash happens due to access to the uninitialized memory when trying to import an FBX file that has animated user properties and multiple clips
Reproduced with: 2017.2.2p1, 2017.3.1p4, 2018.1.0b11, 2018.1.0a4
---------
Fixed in: 2017.4.1f1, 2018.1.0f1, 2018.2.0a6
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
Add comment