Search Issue Tracker
Duplicate
Votes
0
Found in
2020.3
2020.3.7f1
2021.1
2021.2
Issue ID
1334491
Regression
No
Textures remain in RAM even after they've been uploaded to VRAM
Reproduction steps:
1. Open user attached Project
2. Build and Run
3. Press each of the Buttons on the left side
Expected result: VRAM usage increases with each Button
Actual result: RAM AND VRAM usage increases with each Button
Reproducible with: 2020.3.9f1, 2021.1.8f1, 2021.2.0a18
Could not test with: 2018.4, 2019.4 (Compiler errors)
Notes: Read/Write is disabled for all of the Textures
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1354202