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

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


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

android-galaxy-s5

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

Hi rockot@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Revert of Eliminate the ChannelMojo channel for renderers (patchset #4 id:60001 of https://codereview.chromium.org/2109043002/ )
Author  : rockot
Commit description:
  
Reason for revert:
 http://crbug.com/624556 

Original issue's description:
> Eliminate the ChannelMojo channel for renderers, instead obtain Bootstrap interface from child connection.
>
> R=rockot@chromium.org
>  http://crbug.com/623396 
>
> BUG=
>
> Committed: https://crrev.com/9e883c385ccc47607a9341d618678b35195cc8fe
> Cr-Commit-Position: refs/heads/master@{#402812}

TBR=ben@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

Review-Url: https://codereview.chromium.org/2111673006
Cr-Commit-Position: refs/heads/master@{#403205}
Commit  : b44da081cde654f070a29ececea36b33214a7c5e
Date    : Thu Jun 30 17:22:04 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@403181  18370209  110253   5  good
chromium@403197  18304500  139155   5  good
chromium@403201  18295082  147685   5  good
chromium@403203  18284286  242463   5  good
chromium@403204  18349056  107463   5  good
chromium@403205  18939926  87949.8  5  bad    <--
chromium@403213  18934344  99337.1  5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 626178

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.blink_memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:malloc:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:malloc:effective_size_avg
Relative Change: 3.07%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/774
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007839987812426368


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5773849530990592

| 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 Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Revert of Eliminate the ChannelMojo channel for renderers (patchset #4 id:60001 of https://codereview.chromium.org/2109043002/ )
Author  : rockot
Commit description:
  
Reason for revert:
 http://crbug.com/624556 

Original issue's description:
> Eliminate the ChannelMojo channel for renderers, instead obtain Bootstrap interface from child connection.
>
> R=rockot@chromium.org
>  http://crbug.com/623396 
>
> BUG=
>
> Committed: https://crrev.com/9e883c385ccc47607a9341d618678b35195cc8fe
> Cr-Commit-Position: refs/heads/master@{#402812}

TBR=ben@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

Review-Url: https://codereview.chromium.org/2111673006
Cr-Commit-Position: refs/heads/master@{#403205}
Commit  : b44da081cde654f070a29ececea36b33214a7c5e
Date    : Thu Jun 30 17:22:04 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@403181  18262543  208116   5  good
chromium@403197  18284835  128861   5  good
chromium@403201  18222777  220261   5  good
chromium@403203  18438252  204458   5  good
chromium@403204  18316070  222048   5  good
chromium@403205  19023596  91837.4  5  bad    <--
chromium@403213  19012051  136940   5  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 626178

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.blink_memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:malloc:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:malloc:effective_size_avg
Relative Change: 4.10%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/773
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007840000069473152


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5834287505473536

| 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 Tests>AutoBisect.  Thank you!

It's a revert and the graph looks flaky. Closing as WontFix