New issue
Advanced search Search tips

Issue 732914 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add UMA stats for amount of memory used by 2D canvas bitmaps

Project Member Reported by chrishtr@chromium.org, Jun 13 2017

Issue description

1. Amount of memory used by 2D canvas bitmaps
2. Percent of total renderer memory used by #1
3. Breakdown of #2 and #1 by foreground and background tabs

These statistics will help to inform how much of a memory problem there is in
the need to pin these bitmaps to memory, even for backgrounded tabs.
 

Comment 1 by junov@chromium.org, Jun 14 2017

Owner: junov@chromium.org
There should separate stats for RAM vs GPU memory.
There also need to be a break down of where the memory is being held (ex: backing store, compositor, recyclable resource pool) 
Any ideas when this measurement should be taken? at each paint perhaps? do we report this only on pages with canvases?

Cc: ericrk@chromium.org
Eric reports that the GPU process computes its total-memory UMA every 30
seconds on a timer. Perhaps match that?

Only on canvas pages might be ok.
FYI the one for total GPU memory is GPU.ContextMemory.GLES.Periodic
Status: Assigned (was: Available)
Cc: -junov@chromium.org
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment