Search Issue Tracker
Fixed
Fixed in 3.1.6-pre.1
Votes
0
Found in
3.1.5
Issue ID
UUM-133773
Regression
No
GC Allocation of 384 B every frame when using CinemachineInputAxisController
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Open Profiler (Window > Analysis > Profiler)
5. In Profiler search for “CinemachineInputAxisController“
Expected result: GC Alloc of CinemachineInputAxisController is 0 B
Actual result: CinemachineInputAxisController has GC Alloc of 384 B
Reproducible with: 3.1.1 (6000.4.0b7), 3.1.5 (6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a4)
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Not reproducible after deleting the "Demo Control Value Reader" Script Component attached to "VIRTUAL CAMERA"
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