Graphics memory usage on Android is reported separately from everything else, and requires access to memtrack HAL. "dumpsys meminfo" accounts for it and includes it in the total figure.

In order to properly demonstrate improvements in graphics memory (which is one of the biggest memory consumers) on our bots we added libmemtrack_helper tool and code to interface with it (see  issue 529451 ).

However, we still don't report graphics memory to UMA, which is increasingly used to spot regressions and confirm improvements.

In API 23 Android added Debug.MemoryInfo.getMemoryStat("summary.graphics") API, which returns sum of "Gfx dev", "GL mtrack", and "EGL mtrack" values reported by "dumpsys meminfo".

We need to surface that value in UMA.