Search Issue Tracker
Not Reproducible
Votes
1
Found in
2017.2.0f3
Issue ID
978686
Regression
No
Switching the worldCamera of a Canvas allocates memory but never releases it
Steps to reproduce:
1. Open user attached project
2. Open test scene and the profiler window
3. Play the scene
4. Notice the memory usage in the profiler window
5. Select the Camera2 object and uncheck "Allocate Meaningless Memory"
6. Notice how the memory get released fast
Expected result: switching the world camera of a Canvas should allocate memory and release it
Reproduced in: 5.6.5f1, 2017.1.2p4, 2017.2.1p1, 2017.3.0f3, 2018.1.0a7
Not Reproduced in 2019.1.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment