Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
1
Found in
2019.3.0b1
2019.3.6f1
2020.1.0a1
2020.2.0a1
Issue ID
1229421
Regression
Yes
Crash on mecanim::CreateValueArray when setting Animator's Controller to Override Controller with no controller to override
Reproduction steps:
1. Open the user's "David's Adventure in 2D.zip" project
2. Load the "HelloWorld" scene
3. Select the "End" GameObject
4. Change the Animator's Controller "End" to "Fruit"
-- Observe the crash
Reproducible with: 2019.3.0b1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a3
Not reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.0a11
Note: error before the regression was introduced - "Could not set Runtime Animator Controller. The controller Fruit is an AnimatorOverrideController with no AnimatorController to override"
First 5 lines of the stack trace:
0x00007FF7287689F7 (Unity) mecanim::CreateValueArray
0x00007FF72871C42A (Unity) AnimatorControllerPlayable::AllocateBindings
0x00007FF728674E21 (Unity) Animator::CreatePlayableMemory
0x00007FF728674C1E (Unity) Animator::CreateObject
0x00007FF728671CC6 (Unity) Animator::AwakeFromLoad
<...>
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
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
- Context menus open on a different monitor when there are three monitors used
Resolution Note (fix version 2020.2):
Fixed in: 2020.1.0b7, 2020.2.0a8
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.11f1