Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.1f1
Issue ID
887819
Regression
Yes
Memory leak after changing display from UI render camera to main camera
Steps to reproduce:
1. Download "Testmemoryleakui.zip" and open "test-scene" scene
2. Open Profiler window
3. Press play button
4. Press SwitchScreen button
5. Notice GfxDriver in memory profiler starts leaking memory
6. Open Counter.cs and comment out line 14
7. Repeat steps 3-5
8. GfxDriver in memory profiler stops leaking memory
Results: Memory leak happens when UI text's component is updated if UI camera isn't an active camera
Reproduced with: 2017.1.0a2, 5.6.0b10, 5.5.2p2, 5.4.4p4,
Not reproducible with: 5.3.7p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- An Unhandled exception is thrown in the Editor.log and Console window when trying to build AssetBundles
- InterlockedExchange function throws an error when using floats as arguments
Add comment