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

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


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

chromium-rel-mac-retina

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

=== Auto-CCing suspected CL author catapult-deps-roller@chromium.org ===

Hi catapult-deps-roller@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 src/third_party/catapult/ 1d2ebc460..b86cfef4b (2 commits).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/1d2ebc4608d2..b86cfef4b9da

$ git log 1d2ebc460..b86cfef4b --date=short --no-merges --format='%ad %ae %s'
2016-09-13 nednguyen Revert of Revert "[telemetry] Wire TsProxy through telemetry's network stack." (patchset #1 id:1 of https://codereview.chromium.org/2267613002/ )
2016-09-13 benjhayden Fix value-set-table.

BUG=639632

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2340463003
Cr-Commit-Position: refs/heads/master@{#418463}
Commit  : f5d731cca69d998593f42ab79d8eaa26380d7fe3
Date    : Wed Sep 14 02:54:23 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N   Good?
chromium@418456                      1352283  4686.58  18  good
chromium@418460                      1351789  2238.7   5   good
chromium@418462                      1352461  2834.7   5   good
chromium@418462,catapult@b86cfef4b9  1349261  2028.58  5   good
chromium@418463                      1371120  7505.01  5   bad    <--
chromium@418469                      1365125  18985.2  18  bad
chromium@418482                      1365388  21547.8  12  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 647650

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests oortonline_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_avg
Relative Change: 0.93%
Score: 99.5

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


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

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

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.