Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2019.4
2019.4.3f1
2020.1
2020.2
Issue ID
1267356
Regression
No
Silent crash when calling AnimationPlayerState.Initialize
How to reproduce:
1. Open user attached project "AnimationPlayerWork.7z"
2. Open the scene "Animation Player Work Scene".
3. Select "Ellen" GameObject.
4. Find the "AnimationPlayer" component on that object, and expand the only state under "Single Clip States"
5. Press "play" under "Preview" twice
Expected result: Editor does not crash
Actual result: Editor crashes
Reproducible with - 2019.4.7f1, 2020.1.0b16, 2020.2.0a20
Not reproducible with - 2018.4.26f1 (Editor errors)
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
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- [Linux] AutoLocale log is logged when opening a project
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (2021.2.X):
The following code is recursive emptyClip is going to call itself and cause a stack overflow (should use _emptyClip instead in the property getter)
public static AnimationClip emptyClip => (_emptyClip) != null ? emptyClip : (_emptyClip = new AnimationClip())