Search Issue Tracker
Fixed
Fixed in 2022.2.X, 2022.2.16f1
Votes
0
Found in
2022.2.12f1
Issue ID
UUM-31715
Regression
Yes
[MemoryProfiler] Graphics size is not shown for RenderTextures in 1.1.0-exp.1
Steps to reproduce:
1. Open any Project with Unity version 2022.2.x or newer
2. Make sure Memory Profiler Is installed via the manifest to use version 1.1.0-exp.1
3. Open Memory Profiler by going to Window → Analysis → Memory Profiler
4. Import and open the attached memory profiler snapshots
5. Find RenderTexture entries in Unity Objects or All Of Memory table
6. Observe their Native and Graphics sizes in the table and in the Selection Details panel when selected.
Compare these numbers to the numbers shown when using version 1.0 of the Memory Profiler
Expected result: The total memory shown for these should be about the same
Actual result: Their total memory value is shown as drastically decreased.
Reproducible with: 1.1.0-exp.1 (2022.2.7f1, 2023.2.0a7)
Not reproducible with: 1.0.0 (2022.2.7f1, 2023.2.0a7)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment