Search Issue Tracker
Won't Fix
Votes
1
Found in
5.3.2p3
Issue ID
771396
Regression
No
Profiler shows that texture uses twice the amount of memory
To reproduce:
1. Open the attached project
2. Load the "test" scene
3. Hit play
4. Open Profiler window
5. In the Profiler window, select "Memory"
6. Change mode from "Simple" to "Detailed"
7. Click "Take Sample: Editor"
8. Expand "Scene Memory" -> "Texture2D"
Actual result: the texture is using 32 MB of memory. Double clicking it will select the game object and the preview window shows 16 MB (see screenshot)
Expected result: Numbers in the Profiler and the Preview window should be the same
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment