Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.16f1
2021.1
2021.2
2022.1
Issue ID
1370505
Regression
No
ProfilerRecorder does not account the memory usage of textures for Total Used Memory in Non-development Builds
Reproduction steps:
1. Open the user's attached "1103085_Profiler_Memory.zip" project
2. Build and Run the "DemoWithTexture" Scene with a Development Build unselected
3. Observe the Total Used Memory value
4. Build And Run the "DemoNoTexture" Scene with a Development Build unselected
5. Observe the Total Used Memory value
6. Compare observed values
Expected result: Total Used Memory shows bigger memory usage for a "DemoWithTexture" build than a "DemoNoTexture" build
Actual result: Total Used memory shows the 37-38 MB memory usage for both "DemoWithTexture" and "DemoNoTexture" builds
Reproducible with: 2020.3.21f1, 2021.1.27f1, 2021.2.0f1. 2022.1.0a12
Couldn't test with: 2019.4.31f1 (Compilation errors after downgrade)
Note:
- Not reproducible with Development Builds (Total Used Memory accounts for a texture memory in the Build)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2022.1.X):
We don't track graphics allocations in release mode for performance reasons. "Total Used Memory" & "Total Reserved Memory" - as per manual, total value Unity *tracks*.