Search Issue Tracker
Active
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
- [iOS] UI Toolkit's DropdownField fails to close on first tap when Windowed Apps is used
- Frame Count differs in the Frame Debugger after exiting Play Mode with the Frame Debugger Enabled
- VFX System Border text cursor is sometimes not visible
- Hub horizontal scroll hides all items when scrolled to the end
- GC Allocation of 384 B every frame when using CinemachineInputAxisController
Add comment