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

Issue 810293 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

Add ArrayBuffer size to chrome ukm memory

Project Member Reported by yuzus@chromium.org, Feb 8 2018

Issue description

To understand better what is going on with renderer memory usage, we need to add ArrayBuffer size (reported by memory-infra) to chrome ukm log.

 
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 13 2018

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

commit 7a6cb7cdb76a86d4d414ddc0be1f3a9a9f6ef088
Author: Yuzu Saijo <yuzus@chromium.org>
Date: Tue Feb 13 11:03:15 2018

Add ArrayBuffer to UKM Report

This CL adds the size of ArrayBuffer size(MB) to UKM report.
UKM review document: https://docs.google.com/document/d/1WqJEtCoZQIuLaUu55riE4Cwh_9H0a_zRbl7gcGoW-Rs/edit?usp=sharing

BUG=810293

Change-Id: Ifc609c4224b4d380bc52732bf8e23f7dcdb34d28
Reviewed-on: https://chromium-review.googlesource.com/908176
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536332}
[modify] https://crrev.com/7a6cb7cdb76a86d4d414ddc0be1f3a9a9f6ef088/chrome/browser/metrics/process_memory_metrics_emitter.cc
[modify] https://crrev.com/7a6cb7cdb76a86d4d414ddc0be1f3a9a9f6ef088/chrome/browser/metrics/process_memory_metrics_emitter_unittest.cc
[modify] https://crrev.com/7a6cb7cdb76a86d4d414ddc0be1f3a9a9f6ef088/tools/metrics/ukm/ukm.xml

Comment 3 by holte@chromium.org, Apr 25 2018

Components: -Internals>Metrics>UKM
Labels: Hotlist-Metrics
Project Member

Comment 4 by bugdroid1@chromium.org, Aug 6

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

commit b5759a363013856cefd4086ba6ed5f00f889bd15
Author: Takashi Sakamoto <tasak@google.com>
Date: Mon Aug 06 04:39:09 2018

Use size instead of effective_size for partition_alloc.partitions.*

Bug: 810293
Change-Id: I0fdbb07ef9ebf78c964f9ffeb68dc21f9675bdb7
Reviewed-on: https://chromium-review.googlesource.com/1158112
Commit-Queue: Takashi Sakamoto <tasak@google.com>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#580801}
[modify] https://crrev.com/b5759a363013856cefd4086ba6ed5f00f889bd15/chrome/browser/metrics/process_memory_metrics_emitter.cc
[modify] https://crrev.com/b5759a363013856cefd4086ba6ed5f00f889bd15/chrome/browser/metrics/process_memory_metrics_emitter_unittest.cc

Status: Available (was: Started)
This issue has been marked as started, but has no owner. Making available.

Sign in to add a comment