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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
RenderTexture.GetTemporary allocates memory. Call ReleaseTemporary to release the memory. See https://docs.unity3d.com/ScriptReference/RenderTexture.GetTemporary.html for details