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

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


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/video.html?src_crowd2160.mp4

Revision             Result                  N
chromium@504251      72543259 +- 255826      21      good
chromium@504455      72543259 +- 255826      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.crowd2160.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/8966729260057275952


For feedback, file a bug with component Speed>Bisection