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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7LqrugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrInn_ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrLqBqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrITSpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7LiqrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzOmeiwoM


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

android-nexus5
android-nexus7v2
android-one

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

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

Hi ben@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 : ben
  Commit : 649b3edd4d074b63688f31671cf36ca7cb8ff53b
  Date   : Thu Mar 23 00:32:02 2017
  Subject: Begin to wean child processes off reliance on a persistent service_manager::Connection to the browser.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_cnn
  Change       : 1.48% | 20145099.3333 -> 20444149.3333

Revision             Result                  N
chromium@458927      20145099 +- 332777      6      good
chromium@458947      20099197 +- 382333      6      good
chromium@458952      20083379 +- 248707      6      good
chromium@458953      20156472 +- 241331      6      good
chromium@458954      20457597 +- 193564      6      bad       <--
chromium@458955      20619872 +- 269244      6      bad
chromium@458957      20547742 +- 275742      6      bad
chromium@458966      20591235 +- 226327      6      bad
chromium@459005      20444149 +- 336108      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.news.cnn system_health.memory_mobile

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

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


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

This mostly came down eventually.