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

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


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

android-nexus9

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


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384314         48636.0     180.0       5           good
chromium@384339         48815.2     262.50181   5           good
chromium@384610         58071.2     202.235506  5           bad
chromium@384674         57998.4     335.542546  5           bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 600264

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 19.25%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1706
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016325666575219360


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

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

I clicked the link to report a bad bisect for #2, it should have bisected between the middle two revisions or reported why not.

I tried again here: https://chromeperf.appspot.com/buildbucket_job_status/9016217101077382640

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

Hi perkj@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 : Roll WebRTC 12179:12196, Libjingle 12115:12188
Author  : perkj
Commit description:
  
WebRTC 12179:12196

Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/83147bf..f97e5d7

Libjingle 12115:12188

Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/2688852..c5d109d

TBR=
BUG=

Review URL: https://codereview.chromium.org/1850673003

Cr-Commit-Position: refs/heads/master@{#384572}
Commit  : 86d1c393c11c91f99c2dc6346f5512e70d6c183a
Date    : Fri Apr 01 13:49:57 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384339         93966.4     4845.238157 5           good
chromium@384460         92232.8     2481.574339 5           good
chromium@384520         93100.8     2875.90737  5           good
chromium@384550         91864.0     1661.71237  5           good
chromium@384565         90739.5     2116.504328 8           good
chromium@384569         93547.0     2670.90632  8           good
chromium@384571         92500.6666672315.472018 6           good
chromium@384572         101670.0    4015.804112 4           bad         <-
chromium@384573         100368.0    2667.554685 5           bad
chromium@384580         103935.5    3577.959474 8           bad

Bisect job ran on: linux_perf_bisect
Bug ID: 600264

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 8.84%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6373
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016222408301392512


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

| 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 : Roll WebRTC 12179:12196, Libjingle 12115:12188
Author  : perkj
Commit description:
  
WebRTC 12179:12196

Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/83147bf..f97e5d7

Libjingle 12115:12188

Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/2688852..c5d109d

TBR=
BUG=

Review URL: https://codereview.chromium.org/1850673003

Cr-Commit-Position: refs/heads/master@{#384572}
Commit  : 86d1c393c11c91f99c2dc6346f5512e70d6c183a
Date    : Fri Apr 01 13:49:57 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384564         31311.2     285.760739  5           good
chromium@384569         31475.0     173.570351  4           good
chromium@384571         31155.2     390.562671  5           good
chromium@384572         40550.4     321.951549  5           bad         <-
chromium@384574         40454.4     348.098837  5           bad
chromium@384584         41070.0     487.611868  4           bad
chromium@384604         40748.0     543.08747   4           bad
chromium@384644         40623.2     140.039994  5           bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 600264

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests webrtc.peerconnection
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 29.44%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2880
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016217101077382640


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

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

based on bisect results, perkj@ could you please check the issue.

This is a duplicate- and quite unfortunate since it turns out that the android bots do not get a proper call up and running. So even though the graph shows a regression- it is due to refactoring work and is expected. If these tests had actually setup a call- the memory consumption would have been the same.

phoglund - any progress on getting the Android bots to actually get a call up and running? 

Can you please mark this as a duplicatate of the other one?