New issue
Advanced search Search tips

Issue 902383 link

Starred by 1 user
Status: Duplicate
Merged: issue 904996
Owner:
ericrk@chromium.org
Closed: Nov 13
Cc:
ericrk@chromium.org
jrumm...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% regression in media.mobile at 604128:604161

Project Member Reported by jrumm...@chromium.org, Nov 6 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 6 

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

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


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

android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 7

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

EnableGpuRasterizationViewportRestriction bot config by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/924edd7aee62613bf0d3f51b4c4d00e63f5c104e
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 6.576e+06 → 6.531e+06 (-4.529e+04)

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

Benchmark documentation link:
  None

Comment 4 by ericrk@chromium.org, Nov 13

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

Sign in to add a comment