New issue
Advanced search Search tips

Issue 896823 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 899002
Owner:
Closed: Oct 25
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 898270



Sign in to add a comment

7.2%-10.3% regression in memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size at 600385:600423

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 18

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=896823

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=568a13864f75467e93a708b733a552e364d9cc50cb7148c83c97cd095fd8c1f9


Bot(s) for this bug's original alert(s):

linux-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: backer@chromium.org
Owner: backer@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/130ddbcae40000

Bound time to delete cc::Resource by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf42619ce76159d90ab4b968208ad620c042ac2
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 2.077e+08 → 2.32e+08 (+2.43e+07)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Blocking: 898270
Labels: vulkanize
Mergedinto: 899002
Status: Duplicate (was: Assigned)

Sign in to add a comment