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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=2854e69da676f6e5a58f2bd06e281c6f1451028f23995bf094642cff09c00302


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

chromium-rel-mac-retina

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

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

Hi rmcilroy@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 : Ross McIlroy
  Commit : 73ec55982cc13712bce0853ff2a3eeec909e4db6
  Date   : Thu Aug 17 13:21:44 2017
  Subject: Reland "[Compiler] Remove CompileDebugCode and EnsureBytecode and replace with Compile"

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/video.html?src_garden2_10s.mp4
  Change       : 0.48% | 3445225.33333 -> 3461702.66667

Revision                           Result                  N
chromium@495262                    3445225 +- 71567.7      6      good
chromium@495356                    3430364 +- 96810.4      6      good
chromium@495359                    3430771 +- 96215.5      6      good
chromium@495361                    3404376 +- 93289.5      6      good
chromium@495361,v8@0f40415b6b      3458317 +- 1595.42      6      good
chromium@495361,v8@d74ec7efa8      3415333 +- 104737       6      good
chromium@495361,v8@73ec55982c      3461873 +- 1008.79      6      bad       <--
chromium@495361,v8@bbcc4998f9      3463855 +- 8977.12      6      bad
chromium@495362                    3461784 +- 1248.51      6      bad
chromium@495368                    3461791 +- 1529.92      6      bad
chromium@495380                    3461871 +- 1851.8       6      bad
chromium@495403                    3465768 +- 22681.1      6      bad
chromium@495450                    3461703 +- 1008.03      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.garden2.10s.mp4 media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970675428375447296


For feedback, file a bug with component Speed>Bisection

The bisect looks pretty noisy, I'm going to kick off another.

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

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

Hi rmcilroy@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 : Ross McIlroy
  Commit : 21da12a98352e0e31f79d3ae1fa003cacb4ae32c
  Date   : Thu Aug 17 09:47:57 2017
  Subject: [Compiler] Remove CompileDebugCode and EnsureBytecode and replace with Compile

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/video.html?src_garden2_10s.mp4
  Change       : 1.26% | 3418728.0 -> 3461649.33333

Revision                           Result                  N
chromium@495262                    3418728 +- 95217.5      6      good
chromium@495356                    3431645 +- 89715.7      6      good
chromium@495359                    3387059 +- 233438       6      good
chromium@495361                    3363213 +- 297886       9      good
chromium@495361,v8@21da12a983      3463307 +- 8930.04      6      bad       <--
chromium@495361,v8@8ee068388e      3461785 +- 1169.34      6      bad
chromium@495361,v8@0f40415b6b      3449788 +- 74326.9      9      bad
chromium@495361,v8@bbcc4998f9      3460828 +- 6078.21      9      bad
chromium@495362                    3466380 +- 23303.0      6      bad
chromium@495368                    3466233 +- 23446.7      6      bad
chromium@495380                    3461868 +- 1376.73      6      bad
chromium@495403                    3461864 +- 1113.7       6      bad
chromium@495450                    3461649 +- 205.964      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.garden2.10s.mp4 media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970553915582689200


For feedback, file a bug with component Speed>Bisection

Regression has recovered in graphs.

I think this is more accurately WontFix because no change was made as a result of this bug.