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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgosud9woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4unroQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4uDB7QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4oKV9AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4sKH9goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgovOn8QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4rSntAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgoqvgvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgoozb5gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4pLAuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4oW4pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4p35rwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4oj8tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4oj8tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4qL0_ggM


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

android-nexus5
android-nexus6
android-nexus7v2

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

=== Auto-CCing suspected CL author dgozman@chromium.org ===

Hi dgozman@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : dgozman
  Commit : c8abe8c3b07d77195777e07180a4122f4d50246a
  Date   : Fri Apr 21 23:34:49 2017
  Subject: [DevTools] Consolidate overlay-related functionality in Overlay domain

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_m_youtube_com_results_q_science
  Change       : 717.42% | 5235687.33333 -> 42797749.3333

Revision             Result                   N
chromium@466482      5235687 +- 1812213       6      good
chromium@466487      4956769 +- 1580363       6      good
chromium@466488      5051659 +- 1711219       6      good
chromium@466489      42688534 +- 1337557      6      bad       <--
chromium@466490      42853847 +- 1337365      6      bad
chromium@466492      42711797 +- 936337       6      bad
chromium@466501      42597405 +- 356073       6      bad
chromium@466519      42797749 +- 1040038      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile_stress

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

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


| 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!

dgozman, can you take a look at this?

 Issue 714910  has been merged into this issue.