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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_Jyk5wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_KP0_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_KyesAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvKXn5woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_NiaugoM


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_social/load_social_facebook


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.social.facebook system_health.memory_mobile

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

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


| 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/8982620059530730016

Bisects refuse to run. Graphs show a gradual steady climb, so it's unlikely there is a single-CL effect here.

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

Apologies, we fixed an issue with the dashboard that had the side effect of re-running hundreds of old bisects that had been blocked due to the bug. Had to mass delete all jobs. I'll rekick this and if you see any other issues, block on  crbug.com/711039 

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

Hi michaeln@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 : michaeln
  Commit : 32fda6433bcc281eb4794b8715cf44edb3dd1ce2
  Date   : Mon Apr 03 23:05:50 2017
  Subject: Fix visual studio project files around SK_FREETYPE_MINIMUM_RUNTIME_VERSION

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_social/load_social_facebook
  Change       : 0.73% | 18625974.8571 -> 18716899.5556

Revision             Result                  N
chromium@461568      18625975 +- 217000      14      good
chromium@461570      18611314 +- 246597      9       good
chromium@461571      18620871 +- 233755      9       good
chromium@461572      18769010 +- 196434      9       bad       <--
chromium@461575      18698338 +- 360430      21      bad
chromium@461584      18715794 +- 257539      14      bad
chromium@461596      18699849 +- 345866      14      bad
chromium@461623      18716900 +- 197808      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 --story-filter=load.social.facebook system_health.memory_mobile

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

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


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

PTAL

The change to "Fix visual studio project files around SK_FREETYPE_MINIMUM_RUNTIME_VERSION" can't have caused a regression on android. It's a windows specific change.

Bisect couldn't track this down.