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

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


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

android-one

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

=== 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

Revision             Result                  N
chromium@507565      8155997 +- 4533976      21      good
chromium@507618      8489918 +- 611112       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 media.mobile

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

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


For feedback, file a bug with component Speed>Bisection

Seems to be fixed anyways.