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
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
- Decals do not get projected onto a GameObject draw with the Render Objects Renderer Feature when according to Event it should be projected
- The Depth value is not being written correctly in the Scene view when the Full Screen Pass Renderer Feature is applied on a GameObject with the Render Object Feature
- [Quest] Materials are not rendering in Player when "Single Pass Instanced \ Multi-View" is selected and "Surface Type" is set to "Transparent"
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.