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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggunUvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_J28oAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggpjOpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_I-5qwoM


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

android-nexus5
android-nexus6
android-webview-nexus6

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

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus


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 memory.top_10_mobile_stress

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

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


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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background_search/background_search_google

Revision             Result                    N
chromium@463479      109946466 +- 1965335      21      good
chromium@463547      110226652 +- 2846783      21      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=background.search.google system_health.memory_mobile

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

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


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

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

Hi peconn@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 : peconn
  Commit : 3135f76cdd54307839a6440c1c7c5e6af1d61bfa
  Date   : Tue Apr 11 03:20:11 2017
  Subject: Buffer writing TabState.

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/browse_media/browse_media_imgur
  Change       : 3.13% | 17918976.0 -> 18480128.0

Revision             Result                  N
chromium@463479      17918976 +- 231705      6      good
chromium@463513      18008974 +- 431612      9      good
chromium@463514      18399232 +- 400864      6      bad       <--
chromium@463515      18416640 +- 407372      6      bad
chromium@463516      18450944 +- 383790      6      bad
chromium@463518      18391381 +- 441786      6      bad
chromium@463522      18419029 +- 360607      6      bad
chromium@463530      18567168 +- 706643      6      bad
chromium@463547      18480128 +- 444899      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 --story-filter=browse.media.imgur system_health.memory_mobile

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

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


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

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

Looks like this is pretty noisy.