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

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


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

chromium-rel-mac12-mini-8gb

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_10_12_mini_8gb_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.webm_seek

Revision             Result                 N
chromium@483363      4021125 +- 308796      21      good
chromium@483524      4023234 +- 311071      21      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.webm.seek 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/8974706059128985328


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : f341bb0f623821e56349735e47e1a9094f65d9a3
  Date   : Fri Jun 30 12:03:04 2017
  Subject: Revert "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: mac_10_12_mini_8gb_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.webm_seek
  Change       : 8.10% | 3989606.66667 -> 4312877.33333

Revision                           Result                  N
chromium@483363                    3989607 +- 293849       6      good
chromium@483586                    4035193 +- 17586.5      6      good
chromium@483697                    4036989 +- 28990.0      9      good
chromium@483725                    3993596 +- 290558       9      good
chromium@483729                    4034613 +- 22762.9      6      good
chromium@483729,v8@ca93156294      4034305 +- 23373.5      6      good
chromium@483729,v8@f341bb0f62      4315219 +- 1402.98      6      bad       <--
chromium@483729,v8@fa4314da8b      4315692 +- 2109.96      6      bad
chromium@483729,v8@bfbabce113      4315333 +- 1612.78      6      bad
chromium@483730                    4314787 +- 4046.19      6      bad
chromium@483731                    4314599 +- 2630.03      6      bad
chromium@483732                    4314169 +- 2983.76      6      bad
chromium@483739                    4315380 +- 2207.76      6      bad
chromium@483753                    4250045 +- 551417       9      bad
chromium@483808                    4312877 +- 1497.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.webm.seek 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/8974706012508408976


For feedback, file a bug with component Speed>Bisection