Search Issue Tracker
By Design
Votes
3
Found in
2021.3.32f1
2022.3.14f1
2023.2.2f1
2023.3.0a16
Issue ID
UUM-57084
Regression
No
Memory leaks when using the “CommandBuffer” to perform a series of render operations using temporary RenderTextures on iOS devices
How to reproduce:
1. Build And Run the user’s attached “My project.zip” project on iOS device
2. In the app, press the “render” button a few times
3. Observe the memory usage in the Xcode’s Debug navigator
Expected result: After pressing 3 times, Memory usage increases a bit
Actual result: After pressing 3 times, Memory usage is 300-600MB
Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Not reproducible on: No other environment tested
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
RenderTexture.GetTemporary allocates memory. Call ReleaseTemporary to release the memory. See https://docs.unity3d.com/ScriptReference/RenderTexture.GetTemporary.html for details