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

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


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

android-nexus5

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean       Std Dev   N   Good?
chromium@421571  104310189  764434    18  good
chromium@421623  110869249  11662690  18  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 651483

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max
Relative Change: 6.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4163
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000169958800504928


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

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

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

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


===== SUSPECTED CL(s) =====
Subject : [heap] New heuristics for incremental marking step size.
Author  : ulan
Commit description:
  
This patch simplifies code for speeding up marking and
removes write barrier counter.

The step size is now computed based in two parts:
- bytes to mark in order to keep up with allocation,
- bytes to mark in order to make progress.

BUG= chromium:616434 ,  chromium:646139 , chromium:644819
LOG=NO

Review-Url: https://codereview.chromium.org/2359903002
Cr-Commit-Position: refs/heads/master@{#39827}
Commit  : 1beb89f24cb01663843a7519921e7caf0910c760
Date    : Wed Sep 28 13:27:59 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N  Good?
chromium@421571                38116629  1676670  5  good
chromium@421597                37560144  460353   5  good
chromium@421610                38704434  1808344  5  good
chromium@421617                38602168  1309329  5  good
chromium@421619                40640865  735321   5  good
chromium@421619,v8@24ae2955ec  40082843  263066   5  good
chromium@421619,v8@0698f10661  39579696  1681431  5  good
chromium@421619,v8@4c2fd5cd5f  38491746  1517725  5  good
chromium@421619,v8@1beb89f24c  46543024  1605036  5  bad    <--
chromium@421619,v8@669719d5fb  45033877  1868200  5  bad
chromium@421620                46523405  2081327  5  bad
chromium@421623                45586397  2347220  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 651483

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:allocated_objects_size_avg
Relative Change: 19.60%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4223
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999090207358396496


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

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