Search Issue Tracker
Fixed in 2021.3.17f1
Fixed in 2023.1.0a22
Votes
1
Found in
2020.3.39f1
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a9
Issue ID
UUM-13148
Regression
No
AnimatorOverrideController.SendNotification uses most of the CPU and takes ~6ms
Reproduction steps:
1. Open the attached project “Bug Test.zip”
2. Open the Profiler window and enable “Deep Profile”
3. Enter Play mode
4. Select a frame in the CPU module
5. Switch to “Hierarchy” at the bottom of the Profiler window
6. Search for “AnimatorOverrideController.SendNotification”
Expected result: AnimatorOverrideController.SendNotification doesn’t use most of the CPU
Actual result: AnimatorOverrideController.SendNotification uses most of the CPU
Reproducible on: 2020.3.39f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a9
Reproducible with: macOS 12.4 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.3.17f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14753
Resolution Note (fix version 2023.1.0a22):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14753