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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.