Search Issue Tracker
By Design
By Design in 3.0.X
Votes
1
Found in [Package]
2.9.5
3.0.0-pre.3
Issue ID
CMCL-1458
Regression
No
CinemachineBrain component constantly invokes Garbage Collection when enabled
How to reproduce:
1. Open the "cinemachinebrain_gc" project
2. Open the "SampleScene"
3. Open the Profiler (Window > Analysis > Profiler)
4. Enter Play Mode, wait 1 second, and Pause Game mode
5. Observe the CPU Usage section in the Profiler
6. In Hierarchy find "Main Camera" GameObject and enable the "CinemachineBrain" component
7. Unpause Game Mode and wait for 1 second
8. Pause the Game Mode again and observe the Profiler again
Expected result: Garbage Collection does not occur
Actual result: Garbage Collection always occurs when the “CinemachineBrain” component is enabled
Reproduced with: 2.5.0 (2020.3.46f1), 2.6.11 (2020.3.46f1), 2.9.5 (2020.3.46f1, 2021.3.22f1), 3.0.0-pre.4 (2022.2.13f1, 2023.1.0b10, 2023.2.0a8)
Reproduced on: Windows 11
Note: The size of GC is consistently at 368 bytes
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The garbage is not present in builds, it's editor-only.
Resolution Note (3.0.X):
The garbage is not present in builds, it's editor-only.