Search Issue Tracker
Not Reproducible
Not Reproducible in 2023.1.X
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a22
Issue ID
UUM-21614
Regression
No
[Linux] "RenderTextures" data not being included in "Graphics" memory usage in the Memory Profiler
How to reproduce:
1. Open the user-attached project (RenderTextures_1415558_modified (1).zip)
2. Build and Run the Linux Player with "Development Build" enabled
3. In the Editor go to Window > Analysis > Memory Profiler
4. In the top left of the Memory Profiler window open the Editor dropdown and connect the profiler to 127.0.0.1
5. Take a snapshot in the Memory Profiler
6. Wait 10 seconds and take a snapshot of the Player again
7. Compare the two sets of data noting the "Graphics" and "RenderTexture" memory usage
Expected result: the "RenderTexture" memory usage increased along with the "Graphics" memory usage
Actual result: only the "RenderTexture" memory usage increased but not the "Graphics" memory usage
Reproducible with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a22
Could not test with: 2020.3.43f1 (Memory Profiler not available)
Reproducible on: Linux Player
Not reproducible on: Windows Player
Note: When the player starts its best to take the first screenshot as fast as possible else there might not be any difference in the "RenderTexture" memory usage visible between the snapshots
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
- 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
Resolution Note:
The ports are no longer Repo'ing, hence closing this.
Resolution Note (2023.1.X):
The ports are no longer Repo'ing, hence closing this.