This article explains why the Memory Usage graph in the Engine Diagnostics Performance dashboard shows unexpectedly high values. The high memory values are traced to Editor sessions, which report total system memory usage, while deployed builds show significantly lower, realistic application memory usage.
Symptoms:
- The Memory Usage values in the Diagnostics Performance dashboard are extremely high (e.g., 25–35 GB) and do not match the expected in-game memory usage.
- There is confusion about what “Memory used by the application over a session” represents and how to interpret it for tracking memory leaks and peak usage over time.
Cause:
The most common cause for High Memory Usage values appearing in the Performance section is that the data includes locally run Editor sessions. Editor runs a report on total system memory usage (Unity + virtual memory), which can be tens of gigabytes, unlike deployed desktop or mobile builds that typically use under 3 GB.
Resolution:
To obtain meaningful Memory Usage metrics for deployed players, filter the Performance dashboard by released application versions (e.g., specific build numbers), devices, or platforms, and exclude local/Editor versions from the view:
Use the filters in the Performance section so the Memory Usage graph can track average and peak memory usage per session over time and monitor improvements as you address memory leaks.
Additional Information:
Please review the Performance section on the Diagnostics reference.