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

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


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

android-nexus5

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

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

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

=== 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 : 4bf230386429b68cd02e0b1cb8450691f525fc04
  Date   : Fri Apr 28 08:01:32 2017
  Subject: [DevTools] Cleanup overlay resources in Dispose

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 10.55% | 73733461.3333 -> 65957205.3333

Revision             Result                   N
chromium@467921      73733461 +- 150236       6      good
chromium@467926      73855659 +- 698903       6      good
chromium@467927      65955840 +- 92817.6      6      bad       <--
chromium@467928      65922389 +- 80404.1      6      bad
chromium@467930      65923755 +- 80404.1      6      bad
chromium@467938      65933312 +- 74632.7      6      bad
chromium@467954      65957205 +- 3739.12      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

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

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


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

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

Suspected Commit
  Author : kbr
  Commit : 1d44ab0e3d0a7cd05ce1da956bb87a85a8b88174
  Date   : Wed May 03 16:54:08 2017
  Subject: Fix bug in virtualized GL context state management upon creation.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 11.85% | 66087594.6667 -> 73919829.3333

Revision             Result                   N
chromium@468953      66087595 +- 580207       6      good
chromium@468981      65978368 +- 74632.7      6      good
chromium@468995      66056192 +- 699109       6      good
chromium@469002      65957205 +- 3739.12      6      good
chromium@469006      66068480 +- 684461       6      good
chromium@469007      73930069 +- 56952.6      6      bad       <--
chromium@469008      74030421 +- 685133       6      bad
chromium@469009      73919829 +- 92757.3      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

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

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


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

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

Suspected Commit
  Author : kbr
  Commit : 1d44ab0e3d0a7cd05ce1da956bb87a85a8b88174
  Date   : Wed May 03 16:54:08 2017
  Subject: Fix bug in virtualized GL context state management upon creation.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 10.78% | 65942414.2222 -> 73048974.2222

Revision             Result                   N
chromium@468953      65942414 +- 355233       9      good
chromium@468981      66045269 +- 687884       9      good
chromium@468995      66134471 +- 900644       9      good
chromium@469002      66238236 +- 1027975      9      good
chromium@469006      65933995 +- 72214.4      6      good
chromium@469007      73930752 +- 110781       6      bad       <--
chromium@469008      73908224 +- 58502.6      6      bad
chromium@469009      73048974 +- 7526560      9      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

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

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


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