New issue
Advanced search Search tips

Issue 876137 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

9.7% 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=876137

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


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/14c8b906640000

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

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
Sadly the API doesn't work well on Marshmallow so had to be disabled.

Sign in to add a comment