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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : media.mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/video.html?src_tulip2.vp9.webm_seek

Revision             Result                  N
chromium@508976      4984376 +- 1952564      21      good
chromium@509047      5053496 +- 1416538      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.vp9.webm.seek media.mobile

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

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


For feedback, file a bug with component Speed>Bisection