New issue
Advanced search Search tips

Issue 888162 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Sep 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

52.4% regression in media.desktop at 592386:592418

Project Member Reported by chcunningham@chromium.org, Sep 21

Issue description

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

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


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

linux-perf

media.desktop - Benchmark documentation link:
  None
Cc: kylec...@chromium.org
Owner: kylec...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16853c14e40000

Add memory dump support to VizProcessContextProvider. by kylechar@chromium.org
https://chromium.googlesource.com/chromium/src/+/e7eca0a627c8289ec11efd27a26df8fe5c81e7e7
6.040e+06 → 9.27e+06 (+3.229e+06)

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

Benchmark documentation link:
  None
The alert has 1 graph related to memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg.
Mergedinto: 887311
Status: Duplicate (was: Assigned)

Sign in to add a comment