Search Issue Tracker
Fixed in 2021.3.32f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment