Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X, 6000.6.X, 6000.7.X
Votes
0
Found in
6000.0.75f1
6000.3.15f1
6000.4.6f1
6000.5.0b8
6000.6.0a5
6000.7.0a1
Issue ID
UUM-142284
Regression
No
Texture memory does not get released when using Direct3D12 Graphics API
How to reproduce:
1. Open the attached "IN-142722_SmallTexture.zip" project
2. Build the project
3. Run the Player
4. Observe the VRAM graph with the green line in the Player
Actual result: VRAM does not get released when the textures are released
Expected result: VRAM gets released when the textures are released
Reproducible with: 2023.1.0a1, 6000.0.75f1, 6000.3.15f1, 6000.4.6f1, 6000.5.0b8, 6000.6.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- The issue does not reproduce if Direct3D11 is selected in the “Graphics API for Windows” in Project Settings instead of Direct3D12 (tested on 6000.3.15f1 and 6000.6.0a5)
- The issue does not reproduce if “Intel 32-bit” Architecture is selected in the Build Profile settings (tested on 6000.3.15f1 and 6000.6.0a5)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rigidbody prefab in scene is losing overrides on Linear/Angular Damping
- "ObjectDisposedException: SerializedProperty injectionPoint has disappeared!" errors are thrown in the Console and the Renderer Feature addition cannot be undone after performing Undo on a Full Screen Pass Renderer Feature
- Rendering corruption on ARM Mali GPU when using shader with FrameBuffer and DepthTexture with Vulkan API
- TextMeshPro text fails to render on macOS Standalone builds when Canvas Plane Distance is close to the Camera's Near Clip Plane
- info-log.json logs the wrong OS version when using a macOS device
Add comment