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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.