New issue
Advanced search Search tips

Issue 921190 link

Starred by 1 user
Status: Duplicate
Owner:
maxmorin@chromium.org
Closed: Jan 14
Cc:
m...@chromium.org
maxmorin@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2% regression in system_health.memory_desktop at 621444:621569

Project Member Reported by m...@chromium.org, Jan 11 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 11 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=921190

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


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

linux-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 12

Cc: maxmorin@chromium.org
Owner: maxmorin@chromium.org
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10299077940000

Fix audio service quit timeout logic. by maxmorin@chromium.org
https://chromium.googlesource.com/chromium/src/+/f10ae53e17c31f66b1597f535e4ceeacb820ced0
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 9.367e+07 → 9.583e+07 (+2.166e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Comment 4 by maxmorin@google.com, Jan 14

Mergedinto: 921179
Status: Duplicate (was: Assigned)
►

Sign in to add a comment