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
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
- "ShadowCaster2D" Component doesn't work when the "Casting Source" is set to "Polygon Collider 2D"
Add comment