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
- Crash on vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
- Stencil buffer is incorrectly cleared across Vulkan render passes during depth-only clear operations when using CommandBuffer API
- A non-existent webpage is opened when "Learn about Unity Build Automation" hyperlink is clicked
Add comment