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

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


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

chromium-rel-win7-dual
chromium-rel-win8-dual

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@438257  53399075  12032246  21  good
chromium@438273  52589509  15294773  21  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 674597

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.pinterest v8.browsing_desktop_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_media/browse_media_pinterest
Relative Change: 1.52%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2304
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993192080382150624


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

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

Not sure if this is a real regression or only the benchmarks which need to settle a little bit.

This regression is too old to be actionable.