Search Issue Tracker
By Design
Votes
0
Found in
2018.3.3f1
2018.4
2020.2
Issue ID
1122720
Regression
No
Memory remains in use after each update to the Text Element when targetting second Camera Display
How to reproduce:
1. Open the user-submitted project ("Canvas Repro.zip")
2. Build the project and observe its memory usage in the task manager
Expected result: the memory usage says around the same throughout
Actual result: the memory usage steadily climbs and stays in use even when the Play Mode is stopped
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.6f1, 2020.2.0b3
Notes:
1. The issue does not reproduce when all cameras are targeting only Display one
2. The issue also reproduces in Editor
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The memory shoot is due to the presence of more than 1 audio listeners in the scene and the corresponding logging mechanism. Remove all the audio listeners except one and the memory usage remains stable.