Search Issue Tracker
By Design
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a23
Issue ID
UUM-42696
Regression
No
AnimationClip files are too large when they are created
How to reproduce:
1. Open the attached “AnimationClipBug.zip“ project
2. Open the Memory Profiler (Window>Analysis>Memory Profiler)
3. Select the Screenshot on the left of the Memory Profiler window
4. Select the “Object and Allocations“ tab
5. Go to the Object list view and sort descending by size
6. Find an AnimationClip named “IdleBase”
Expected result: Size of the AnimationClip is around 0 bytes
Actual result: Size of the AnimationClip is 4.7 kilobytes
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23
Reproduced on: macOS 13.4.1 (Intel, M1)
Note: If creating a new AnimationClip, the size of it may change depending on the minimum block size of your computer's disk format
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
The animation clip also contains more data than just the curves, there is a basic cost of 3.7 kb just for the animation clip class and all the aggregated data inside the animation clip. So an empty clip with no curve still cost 3.7 kb.