New issue
Advanced search Search tips

Issue 876438 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.3% regression in media.mobile at 584108:584164

Project Member Reported by jrumm...@chromium.org, Aug 21

Issue description

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

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


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

android-nexus5x-perf
Cc: dalecur...@chromium.org
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11879036640000

Bump minimum supported API for setCallback to Nougat. by dalecurtis@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf3d3f50ce7435155cec3ace7418a5b4a7c4109
156 → 174.2 (+18.26)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
WontFix just like the last one, API is busted on M, so we can't use it until N.
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/169d0736640000

Bump minimum supported API for setCallback to Nougat. by dalecurtis@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf3d3f50ce7435155cec3ace7418a5b4a7c4109
156.9 → 173.9 (+16.99)

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

Sign in to add a comment