New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 651095 link

Starred by 1 user
Status: Fixed
Owner:
█ rkaplow@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
skare@chromium.org
isherman@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Need a renderer memory metric that tracks all renderers

Project Member Reported by rkaplow@chromium.org, Sep 28 2016 
We have a renderer metric that only tracks "regular" renderer processes, and ignores extension renderer, chrome:// renderer, etc. Because we mainly look at this metric, we often ignore these other renderer processes.

We should have a higher level renderer metric that all the sub-metrics can roll up to
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 29 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8543a4f3d56b771bd13c97df5b3b87ef769679be

commit 8543a4f3d56b771bd13c97df5b3b87ef769679be
Author: rkaplow <rkaplow@chromium.org>
Date: Thu Sep 29 15:53:40 2016

Add Memory.RenderAll metrics to track renderers at a higher level.

While I was here, I did the planned obsoletion of Memory.Total. Total2 is good.

Owners were suggestions from thread "Memory metrics owners".
Happy to fix for other memory metrics if you would like, or you can it yourselves.

BUG= 651095 

Review-Url: https://codereview.chromium.org/2375083002
Cr-Commit-Position: refs/heads/master@{#421831}

[modify] https://crrev.com/8543a4f3d56b771bd13c97df5b3b87ef769679be/chrome/browser/metrics/metrics_memory_details.cc
[modify] https://crrev.com/8543a4f3d56b771bd13c97df5b3b87ef769679be/tools/metrics/histograms/histograms.xml

Comment 2 by dtapu...@chromium.org, Nov 1 2017

Components: Internals>Metrics

Comment 3 by rkaplow@google.com, May 22 2018

Status: Fixed (was: Assigned)
►

Sign in to add a comment