Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.14f1
2021.1
2021.2
2022.1
Issue ID
1351876
Regression
No
Unity crashes when HumanPoseHandler.SetHumanPose is called after its Animator is destroyed
Reproduction steps:
1. Open the attached project "SetHumanPose.zip"
2. Open the "Main" Scene
3. Enter Play Mode
4. Press the R key
Expected result: Unity does not crash and an error is shown
Actual result: Unity crashes
Reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b4, 2022.1.0a3
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a6