Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b14
Issue ID
649577
Regression
No
When Animator Window visible - it uses 10 - 20 % of CPU
When Animator Window visible - it uses 10 - 20 % of CPU
2) How can we reproduce it using the example you attached
1 Create new project or use attached (scene testScene)
2 Create cube
3 Open animation window and create new animation clip
4 Press "Add Curve" and add Cube:Position
5 Save the scene
6 Open Task Manager (on Windows) and in Processes tab find Unity.exe and notice that it uses 00 - 01 % of CPU
7 Create new scene - notice that Unity.exe uses 10 - 20 % of CPU
8 Make Animator Window not visible (by opening some other tab) - notice that Unity.exe uses 00 - 01 % of CPU again
9 Make Animator Window visible again - notice that Unity.exe uses 10 - 20 % of CPU again
Please see attached video
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
Add comment