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

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


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

chromium-rel-mac-retina

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

===== 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@416467  10884235  615600   18  good
chromium@416471  11490585  1259388  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 644083

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_avg
Relative Change: 3.65%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1632
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002363290852230304


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

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

LO space regressions from changing page size 1M->512k

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

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

Hi hpayer@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 : Fix wrong state of IsolateInBackgroundNotification and IsolateInForegroundNotification.
Author  : hpayer
Commit description:
  
BUG= chromium:636368 , chromium:635965 , chromium:634900 

Review-Url: https://codereview.chromium.org/2245483004
Cr-Commit-Position: refs/heads/master@{#38598}
Commit  : b992a8e1899091e3c180a050c1a63fa1e29886d5
Date    : Fri Aug 12 08:13:56 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N   Good?
chromium@406345                50610682  3212121  12  good
chromium@409925                50092948  4208527  12  good
chromium@410820                69946303  5087570  5   good
chromium@411270                66082248  2979836  5   good
chromium@411493                66920172  1209293  5   good
chromium@411549                64542418  3123058  5   good
chromium@411577                67695157  1595066  5   good
chromium@411591                67281959  3981182  5   good
chromium@411592                66722936  3733284  8   good
chromium@411592,v8@64658b6c28  65986219  3028145  8   good
chromium@411592,v8@e6e32315cc  68301368  2610991  5   good
chromium@411592,v8@b992a8e189  47702859  1612512  5   bad    <--
chromium@411593                49508342  6035807  5   bad
chromium@411595                47854321  1072233  5   bad
chromium@411598                46735305  593736   5   bad
chromium@411605                47888539  1048661  5   bad
chromium@411716                46775998  1091415  8   bad
chromium@413506                47321958  3310837  12  bad
chromium@420666                46908162  1356726  8   bad

Bisect job ran on: win_perf_bisect
Bug ID: 644083

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:allocated_objects_size_avg
Relative Change: 10.00%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6950
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000180881974392192


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

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