Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.4.0f1
2018.1.0a1
2018.2.0a1
2018.2.2f1
Issue ID
1098701
Regression
No
Crash when using certain uninitialized AnimatorControllerPlayable methods
How to reproduce:
1. Download, extract and open user's attached project (Crash.zip)
2. Open 'SampleScene' scene
3. Enter play mode
-- observe the crash
Reproducible with: 2017.4.16f1, 2018.1.9f2, 2018.2.17f1
Not reproducible with: 2018.3.0b11, 2019.1.0a9
Note: Some of the examples - AnimatorControllerPlayable.GetFloat(int index), AnimatorControllerPlayable.GetBool(int index), AnimatorControllerPlayable.GetInteger(int index).
(Unity) AnimatorControllerPlayableBindings::GetIntegerID
(Unity) AnimatorControllerPlayable_CUSTOM_GetIntegerID
(Mono JIT Code) (wrapper managed-to-native) UnityEngine.Animations.AnimatorControllerPlayable:GetIntegerID (UnityEngine.Playables.PlayableHandle&,int)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment