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

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


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

chromium-rel-mac10
linux-release

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

===== 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@405708  2883584  0.0      12  good
chromium@405718  2916352  59279.5  12  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 629107

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:blink_gc:effective_size_avg/load_social_instagram
Relative Change: 0.91%
Score: 0

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


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

| 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/9006717376723704640

Wider bisect: https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2216

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

===== 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@405708  2894507  37837.2  12  good
chromium@405725  2883584  0.0      12  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 629107

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:blink_gc:effective_size_avg/load_social_instagram
Relative Change: 0.00%
Score: 0

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


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

| 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/9003876158031212816

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


===== SUSPECTED CL(s) =====
Subject : Make WebTraceLocation be an alias of tracked_objects::Location
Author  : tzik
Commit description:
  
Make WebTraceLocation be an alias of tracked_objects::Location and
BLINK_FROM_HERE be an alias of FROM_HERE as well. So that tasks posted
from Blink leaves a valid program counter and line number in the crash
dump.

Review-Url: https://codereview.chromium.org/2137013002
Cr-Commit-Position: refs/heads/master@{#405736}
Commit  : 3c109dd65c1984237444da93f7c7acc8b0bdcd92
Date    : Fri Jul 15 09:53:07 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405539  2883584  0.0      5  good
chromium@405729  2909798  58617.2  5  good
chromium@405735  2883584  0.0      5  good
chromium@405736  3014656  0.0      5  bad    <--
chromium@405737  3014656  0.0      5  bad
chromium@405738  3014656  0.0      5  bad
chromium@405741  3014656  0.0      5  bad
chromium@405753  3014656  0.0      5  bad
chromium@405777  3014656  0.0      5  bad
chromium@405824  3014656  0.0      5  bad
chromium@405918  3014656  0.0      5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 629107

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:blink_gc:effective_size_avg/load_social_instagram
Relative Change: 4.55%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2318
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003876158031212816


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

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