New issue
Advanced search Search tips

Issue 777519 link

Starred by 1 user
Status: Assigned
Owner:
schenney@chromium.org
Cc:
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome , Mac
Pri: 3
Type: Task



Sign in to add a comment

Review Compositing.Renderer.PictureMemoryUsageKb metrics implementation

Project Member Reported by wkorman@chromium.org, Oct 23 2017 
The metric has looked wild on CrOS and Mac for since Sep 2017. Previous investigation hasn't turned up anything notable, see issue 768604 for example.

It's not apparent why we only see this on CrOS, and now Mac, which began to show similar memory usage trailing CrOS a bit.

Filing this issue to review how we track picture memory usage, since I recall there were some TODOs and it's known to be done imperfectly. Perhaps there's something obvious where we're doing things wrong/differently by platform and we can clean it up and improve the metric quality.
Project Member

Comment 1 by sheriffbot@chromium.org, Oct 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by schenney@chromium.org, Oct 24

Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
►

Sign in to add a comment