New issue
Advanced search Search tips

Issue 888647 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-17% regression in media.mobile at 592806:593051

Project Member Reported by dalecur...@chromium.org, Sep 24

Issue description

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf
android-nexus5x-perf
mac-10_12_laptop_low_end-perf

media.mobile - Benchmark documentation link:
  None

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

[Media Controls] Move doubletap handling to MediaControlsImpl by steimel@chromium.org
https://chromium.googlesource.com/chromium/src/+/2dfe550c2ef6712eecc39e0702246d27648bb646
2.813e+07 → 3.372e+07 (+5.589e+06)

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

Benchmark documentation link:
  None
Cc: beccahughes@chromium.org
+beccahughes@ as she worked on similar bugs in the past.

Sign in to add a comment