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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgopeW-AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4vK1uQsM


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

android-nexus5
android-nexus6

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

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

Hi dpranke@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 : dpranke
  Commit : c1bc835e0ead2a64955b96ebde29ea191280f99e
  Date   : Sun Apr 23 06:33:52 2017
  Subject: Revert of [DevTools] Consolidate overlay-related functionality in Overlay domain (patchset #7 id:120001 of https://codereview.chromium.org/2819183002/ )

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 0.79% | 6236852.33333 -> 6286110.85714

Revision             Result                  N
chromium@466555      6236852 +- 141558       12      good
chromium@466556      6227632 +- 116160       9       good
chromium@466557      6285599 +- 3481.18      14      bad       <--
chromium@466559      6286111 +- 3851.26      14      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/8981387116823183040

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


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

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

I kicked off another bisect, Dirk's change seems within the noise

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

Suspected Commit
  Author : dpranke
  Commit : c1bc835e0ead2a64955b96ebde29ea191280f99e
  Date   : Sun Apr 23 06:33:52 2017
  Subject: Revert of [DevTools] Consolidate overlay-related functionality in Overlay domain (patchset #7 id:120001 of https://codereview.chromium.org/2819183002/ )

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 1.17% | 6212621.77778 -> 6285980.0

Revision             Result                  N
chromium@466555      6212622 +- 52580.4      9      good
chromium@466556      6226718 +- 131820       9      good
chromium@466557      6285364 +- 3256.51      9      bad       <--
chromium@466559      6285980 +- 1360.81      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/8981338064063970416

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


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

How do we deal w/ regressions that are caused by having to revert a change that broke things? WontFix them?

WontFix but cc the original author. +dgozman FYI