Search Issue Tracker
Fixed in 2.6.2-preview.1
Votes
0
Found in [Package]
2.6.1
Issue ID
1272386
Regression
Yes
[Cinemachine] Huge Memory allocation increase each time when switching between Virtual Cameras
How to reproduce:
1. Open attached "CinemachineBugRepro.zip" project and "SampleScene" scene
2. Select the VirtualCamera_2 GameObject in the Hierarchy window
3. Toggle It On and Off multiple times
Expected result: Unity response time does not change
Actual result: Unity response time increases each time the active state is toggled
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1 (Cinemachine 2.6.0, 2.6.1)
Not reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1 (Cinemachine 2.3.3 - 2.5.0)
Could not test with: 2018.4.26f1 (could not downgrade)
Notes: The issue only occurs if the Camera with the CinemachineBrain component also has a PostProcessLayer component attached
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
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
- Decals do not get projected onto a GameObject draw with the Render Objects Renderer Feature when according to Event it should be projected
Resolution Note (fix version 2.6.2-preview.1):
This was a regression introduced in 2.6.0. Memory leak in CinemachinePostProcessing.OnCameraCut.