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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_media/browse_media_youtube

Revision             Result                   N
chromium@492591      15068161 +- 60645.4      21      good
chromium@492633      15061724 +- 71854.1      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=browse.media.youtube system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Dmitry Gozman
  Commit : 17ffda1a19434a08a8ec98c947b60c2bb90046e1
  Date   : Tue Aug 08 05:20:56 2017
  Subject: [DevTools] Force TouchEventFeatureDetection when enabling touch

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_media/browse_media_youtube
  Change       : 1.01% | 14938663.3333 -> 15088961.3333

Revision             Result                   N
chromium@492517      14938663 +- 45016.4      6      good
chromium@492528      14950945 +- 19761.5      6      good
chromium@492534      14947527 +- 20279.8      6      good
chromium@492537      14941908 +- 30173.4      6      good
chromium@492538      14941572 +- 44693.9      6      good
chromium@492539      15110409 +- 59005.0      6      bad       <--
chromium@492561      15097043 +- 34660.8      6      bad
chromium@492606      15101049 +- 11405.4      6      bad
chromium@492694      15088961 +- 74595.7      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=browse.media.youtube system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection