Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.34f1
2020.3
2021.2
2022.1
2022.2
Issue ID
1397656
Regression
No
GetRuntimeMemorySizeLong returns incorrect size when in Play Mode
How to reproduce:
1. Open the user's attached project
2. Open "SampleScene" Scene
3. Enter Play Mode
Expected result: 4MB is displayed
Actual result: 8MB is displayed
Reproducible with: 2019.4.36f1, 2020.3.27f1, 2021.2.11f1, 2022.1.0b6, 2022.2.0a4
Notes:
- Not reproducible in Player (4MB is outputted)
- Not reproducible in WebGL build (4MB is outputted)
- The size is displayed correctly in the Inspector window
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:
Hello! This is by design. When running in the editor, we keep the CPU copy of textures around at all times, which means the resulting size may be double what was expected (CPU+GPU). Our documentation notes that Editor memory is expected to be different to the "real world" of built Players, but we'll look into updating the docs to make this specific case more clear.