Search Issue Tracker
Third Party Issue
Unknown (hidden) 2019.4.X, 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
Votes
0
Found in
2019.4.39f1
2020.3.35f1
2021.3.4f1
2022.1.4f1
2022.2.0a16
Issue ID
UUM-4403
Regression
No
Staging Textures are not released on DirectX 11 when in Player
How to reproduce:
- Open the attached project "StagingTexturesRepro.zip"
- Open the Player Settings (Edit > Project Settings... > Player)
- Make sure the Graphics API is set to DirectX 11
- Open the Build Settings (Edit > Build Settings...) and Build
- Open the RenderDoc and launch the Player
- Set the RenderDoc to capture 10 sequential frames after 1 second
- Click on “Capture After Delay”
- Switch to the Player and click on the "Create T2DA" button
- Go back to RenderDoc and select one of the frames after the button was clicked
- Check the Resource Inspector (Render Doc > Window > Resource Inspector) and notice the many “2D Texture XXXX” textures. These are the staging textures.
Expected result: The staging Textures are automatically released
Actual result: The staging Textures are not released
Reproducible with: 2019.4.38f1, 2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a16
Tested on: Windows 10 Enterprise
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The textures are correctly freed as per comment.
When giving the textures a special debug name when they are deleted that name is visible in the renderdoc list. As in they are correctly released. It's only renderdoc resource list that is affected if the moment of their usage has been captured.
A bug should be filed against renderdoc if the resource list needs to be used for tracking memory usage.