Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.12f1, 2023.1.17f1, 2023.2.0b11, 2023.3.0a6
Votes
1
Found in
2021.3.31f1
2022.3.2f1
2023.1.15f1
2023.2.0b9
2023.3.0a1
Issue ID
UUM-43697
Regression
No
Player leaking memory when using CubemapArrays and RenderTextures
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the Memory Profiler window (Window > Analysis > Memory Profiler)
3. Build and Run the project (File > Build and Run)
4. Make sure the Player is selected in the Memory Profiler window and then capture a Snapshot
5. In the player press the “New Game” button
6. After everything is loaded go to “Pause Menu” by pressing the ESC button
7. Press the “Back To Menu” button
8. Repeat step 4
9. Observe the Memory Profiler window by comparing the two taken snapshots
Expected result: The “Memory Usage On Device” value is the same for both snapshots
Actual result: The “Memory Usage On Device” value is higher on the second snapshot
Reproducible with: 2022.3.2f1, 2023.3.0a1
Reproducible on: Windows 10, Steamdeck (Reported)
Notes:
- The more times steps 5-7 are repeated, the bigger memory usage will be
- Was not able to test other versions because of the large project size
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment