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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyLf5rQsM


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

chromium-rel-win8-dual

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988655052492555376

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/http___sports.yahoo.com_

Revision             Result                  N
chromium@447549      7.03957 +- 2.53303      21      good
chromium@447621      10.2577 +- 18.3111      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...sports.yahoo.com. smoothness.top_25_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988655052492555376

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5016596310917120


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988639269636972640

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988639264405040064

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/http___sports.yahoo.com_
  Change       : 70.38% | 6.65285714286 -> 10.6543571429

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/12a5a0b5a474a24c6943aef3686d91199a2e2b58..2cd69789c0cc1bf7b35f6c5673ba1db6f2273cf0


Revision             Result                  N
chromium@447549      6.65286 +- 2.48757      14       good
chromium@447585      6.74443 +- 2.562        14       good
chromium@447590      6.77379 +- 2.35799      14       good
chromium@447591      ---                     ---      build failure
chromium@447592      ---                     ---      build failure
chromium@447593      11.0808 +- 14.3055      14       bad
chromium@447594      11.5676 +- 12.4878      14       bad
chromium@447603      11.2704 +- 17.5054      21       bad
chromium@447621      10.6544 +- 13.3011      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...sports.yahoo.com. smoothness.top_25_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988639269636972640

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6721638936084480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg

Revision             Result                   N
chromium@447611      12186561 +- 1729560      21      good
chromium@447695      12235753 +- 1435897      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988639264405040064

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6739557069881344


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982659751796987568

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/http___sports.yahoo.com_

Revision             Result                  N
chromium@447549      6.91824 +- 2.31011      21      good
chromium@447621      8.68657 +- 15.1753      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...sports.yahoo.com. smoothness.top_25_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982659751796987568

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5016596310917120


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.