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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
This is a duplicate of issue #1354202