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

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


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

android-nexus5

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

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

Hi wangxianzhu@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 : wangxianzhu
  Commit : 8cc1739f3017dca5bc97d2721bcdfc903eaec6ec
  Date   : Wed Feb 22 07:11:36 2017
  Subject: Reduce the requirement for saving previousLocation

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 2.16% | 70938624.0 -> 72470528.0

Revision             Result                   N
chromium@451894      70938624 +- 2993366      14      good
chromium@451903      70954098 +- 2431698      9       good
chromium@451906      71005070 +- 2624112      9       good
chromium@451907      71170731 +- 2251315      6       good
chromium@451908      72485092 +- 123576       9       bad       <--
chromium@451912      72477810 +- 61787.9      9       bad
chromium@451929      72470528 +- 0.0          6       bad
chromium@451964      72470528 +- 0.0          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=browse.news.qq system_health.memory_mobile

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

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


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

There seems no direct relation between the blink optimization and gpu memory. May be just accidental. WontFix because the change is trivial.