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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9uDKvwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9v3P9goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9v6DhggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9sK86AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtp_kvwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtt3T4ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9tTT_AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9rqVmwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9uHWqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtt-rqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9tTF3QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtvvqugkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtq2S8AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9qrGrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9vSK6QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtt3F_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtvOCwgkM


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

android-nexus5
chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

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

Hi cbruni@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Camillo Bruni
  Commit : 015edc60ff86b51a4bbf9ce11732ee5bb36245b2
  Date   : Fri Jun 16 10:43:19 2017
  Subject: [runtime] Don't store object literal boilerplates on first run

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:heap:old_space:effective_size_avg/video.html?src_tulip2.ogg_type_audio
  Change       : 17.40% | 2510848.0 -> 2947754.66667

Revision                           Result                 N
chromium@480039                    2510848 +- 0.0         6      good
chromium@480062                    2510848 +- 0.0         6      good
chromium@480073                    2510848 +- 0.0         6      good
chromium@480076                    2510848 +- 0.0         9      good
chromium@480076,v8@97b8ab3342      2510848 +- 0.0         6      good
chromium@480076,v8@015edc60ff      2947755 +- 478607      6      bad       <--
chromium@480076,v8@e48a2ef590      2947755 +- 478607      6      bad
chromium@480077                    2860373 +- 741455      9      bad
chromium@480078                    2947755 +- 478607      6      bad
chromium@480079                    2947755 +- 478607      6      bad
chromium@480084                    2918628 +- 653902      9      bad
chromium@480128                    2947755 +- 478607      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.ogg.type.audio media.tough_video_cases_tbmv2

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976339649858532672

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5707187420135424


| 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 Speed>Bisection.  Thank you!

bi-modal benchmark, this seems to be more GC-timing related.
The values jump back to the previous low with (13d38e4 Version 6.1.19) which does not change anything on V8-side.