Search Issue Tracker
Fixed in 2.6.2-preview.1
Votes
0
Found in [Package]
2.6.1
Issue ID
1279939
Regression
No
Memory leak when changing CinemachineVirtualCamera's Status property from "Standby" to "Live" in Timeline with Playhead
How to reproduce:
1. Unzip the user's attached "Repro_910125.zip" project
2. Delete the Library folder from the project
3. Open the unzipped project
4. Open the "Repro_910125" Scene
5. Search for the "Starting Timeline 1" GameObject in the Hierarchy window
6. Select the "Starting Timeline 1" GameObject in the Hierarchy window
7. Open the Timeline window
8. Select the Cinemachine track in the Timeline window
9. Notice that the CinemachineVirtualCamera Component's Status property is set to "Standby" (It changes to "Live" on 1 frame)
10. Drag the Playhead from the start of the Cinemachine track to where it ends (See attached "1279939_repro.mp4")
11. Observe the Memory usage in the Task Manager
Expected result: Memory usage stays the same when CinemachineVirtualCamera's Status property is changing from "Standby" to "Live"
Actual result: Memory usage goes as high as 12 GB when CinemachineVirtualCamera's Status property is changing from "Standby" to "Live"
Reproducible with: 2.6.1 (2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b4)
Not reproducible with: 2.6.2-preview.1 (2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b4)
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 (fix version 2.6.2-preview.1):
Fixed in: 2.6.2-preview.1