Regarding GL and EGL memory in Chrome on Android.

[Sohan Jyoti]

Hi,

Can we have details of what exactly GL and EGL mtrack represent in adb dumpsys meminfo ?

What we know is GL mtrack deals mostly with driver details of graphics memory while the EGL reflects more on the browser usage ? Is this correct ?

http://www.chromium.org/developers/testing/multi-process-ram-usage-analysis-on-android does help, but not very detailed graphics memory consumption.

Do we need to consider sum of gl and egl mtrack memory for the processes (browser, gpu), to consider graphics memory impact ? There will be some overlaps still ?

Thanks,

Sohan

[Alexandre Elias]

GL mtrack is driver-reported GL memory usage.  It's primarily the sum of GL texture sizes, plus fixed global driver RAM overheads.

EGL mtrack is gralloc memory usage.  It's the sum of the sizes of SurfaceView/TextureViews, and corresponds to the surface buffers dumped in "adb dumpsys SurfaceView".

They don't overlap and you should consider the sum.

(Some devices report another category called "Graphics".  You should ignore that one if you see it, it double-counts a part of GL mtrack.)

[Alexandre Elias]

On Wed, Jan 20, 2016 at 10:57 AM, Alexandre Elias <ael...@chromium.org> wrote:

GL mtrack is driver-reported GL memory usage.  It's primarily the sum of GL texture sizes, plus fixed global driver RAM overheads.

EGL mtrack is gralloc memory usage.  It's the sum of the sizes of SurfaceView/TextureViews, and corresponds to the surface buffers dumped in "adb dumpsys SurfaceView".

Sorry, I meant "adb shell dumpsys SurfaceFlinger".

[Sohan Jyoti]

Thanks that helps :)