Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b5
Issue ID
920101
Regression
Yes
Animator Controller crash when adding an animation for a motion field 'AnimationClipPlayable::ProcessAnimationTargetMatchPass'
Steps to reproduce:
1. Open attached project
2. Open the player animation controller
3. Select the blend tree that has no transitions
4. Add a new motion field
5. Observe the crash/freeze
0x0000000140B66EB3 (Unity) AnimationClipPlayable::ProcessAnimationTargetMatchPass
0x0000000140B68CA0 (Unity) AnimationMixerPlayable::MixerProcess
0x0000000140B68EAE (Unity) AnimationMixerPlayable::ProcessRootMotion
0x0000000140B68CA0 (Unity) AnimationMixerPlayable::MixerProcess
0x0000000140B68EAE (Unity) AnimationMixerPlayable::ProcessRootMotion
...
Expected result: editor should not crash at this point
Reproduced in: 2017.2.0a3, 2017.1.0b9, 2017.1.0a1
Not reproduced in: 5.6.1p3, 5.5.4f1
Regression since: 2017.1.0a1
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
This is a duplicate of issue #909671