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

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


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

android-nexus7v2

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

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

=== 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_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_media/load_media_google_images
  Change       : 11.17% | 69213622.8571 -> 76944530.2857

Revision             Result                    N
chromium@469002      69213623 +- 890008        14      good
chromium@469005      69337673 +- 1048942       14      good
chromium@469006      69125461 +- 327680        9       good
chromium@469007      76902400 +- 8543938       6       bad       <--
chromium@469008      75349561 +- 12496746      9       bad
chromium@469013      75207046 +- 19877467      21      bad
chromium@469023      75043986 +- 16426146      14      bad
chromium@469043      76869632 +- 8378746       6       bad
chromium@469084      75736795 +- 15584360      14      bad
chromium@469166      76944530 +- 12066829      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 --story-filter=load.media.google.images system_health.memory_mobile

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

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


| 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 but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_media/load_media_google_images
  Change       : 9.29% | 69238198.8571 -> 75670089.1429

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1547f4c5289b094a0d0487e6c54297cede4d5db7..9888c32790d9934ce4a4446349c9a691536561cd


Revision             Result                    N
chromium@469002      69238199 +- 943234        14       good
chromium@469005      69303735 +- 1047853       14       good
chromium@469006      69136384 +- 182445        6        good
chromium@469007      ---                       ---      build failure
chromium@469008      77670107 +- 8873138       14       bad
chromium@469013      74945682 +- 20628875      21       bad
chromium@469023      74993664 +- 16317917      14       bad
chromium@469043      76234297 +- 11487224      9        bad
chromium@469084      76793173 +- 8407807       6        bad
chromium@469166      75670089 +- 15532277      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 --story-filter=load.media.google.images system_health.memory_mobile

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

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


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