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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3KitpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnNKbowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnMzPygoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnM-KmgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnOCh3AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3L2qoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3Pqq5gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3JSF9gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3NKWuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7NbR0wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnN3R5QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnOOQ0wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnMWlrAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnNCamQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnMC_twsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IPdhAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnNGn6gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnIGY-AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnIvhpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3OD_oQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7NbR0woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLa0-QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3Ibm-AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnN_prAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnNLR9QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnMuZuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKCXmAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnPzE5gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3Pq0uwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnMC_twkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MOQjAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnOGkvQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnI-YqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnLDWiggM


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

android-nexus6
android-webview-nexus5X
android-webview-nexus6

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

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

Suspected Commit
  Author : tzik
  Commit : e5de8d551e80115b21e0e3ca7d5451d3cee6f3ba
  Date   : Thu Mar 30 18:05:46 2017
  Subject: Clear PostTaskAndReply task on the destination thread

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_social/load_social_tumblr
  Change       : 4.19% | 36405073.3333 -> 37928854.6667

Revision             Result                   N
chromium@460728      36405073 +- 1096340      6      good
chromium@460803      36140075 +- 1576518      6      good
chromium@460813      36046805 +- 1038997      6      good
chromium@460818      36257087 +- 1263787      6      good
chromium@460820      36266268 +- 483116       6      good
chromium@460821      38079627 +- 857712       6      bad       <--
chromium@460822      38289700 +- 1381614      6      bad
chromium@460841      38262744 +- 1115997      6      bad
chromium@460878      37928855 +- 775747       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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.tumblr system_health.memory_mobile

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

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


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