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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : cpu_time_percentage_avg/load_media/load_media_google_images

Revision             Result                     N
chromium@499393      0.252924 +- 0.016094       21      good
chromium@499395      0.252864 +- 0.0217025      20      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=load.media.google.images system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Graph recovers.