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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/load_games/load_games_bubbles

Revision             Result                      N
chromium@485599      133507482 +- 15764235       21      good
chromium@485672      121204268 +- 180753577      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.bubbles 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/8974178131289589024


For feedback, file a bug with component Speed>Bisection

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

=== Auto-CCing suspected CL author altimin@chromium.org ===

Hi altimin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Alexander Timin
  Commit : 214a2f9dd64151cfb5626020d8ba74f2d72012a2
  Date   : Wed Jul 12 01:19:03 2017
  Subject: [scheduler] Refactor renderer scheduler policies.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_social/browse_social_tumblr_infinite_scroll
  Change       : 11.49% | 127388970.286 -> 147438963.429

Revision             Result                     N
chromium@485345      127388970 +- 38577430      14      good
chromium@485580      120572454 +- 23795222      9       good
chromium@485697      124974232 +- 42817238      14      good
chromium@485755      122531252 +- 34478284      9       good
chromium@485758      128922995 +- 47345248      14      good
chromium@485759      132683197 +- 55453428      14      good
chromium@485760      151728646 +- 51150919      14      bad       <--
chromium@485764      147603437 +- 24923958      9       bad
chromium@485771      145606467 +- 24514691      6       bad
chromium@485785      147858413 +- 31468809      9       bad
chromium@485814      147438963 +- 44309182      14      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.social.tumblr.infinite.scroll 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/8970629363342544880


For feedback, file a bug with component Speed>Bisection

Seems that https://chromium-review.googlesource.com/573902 fixed this too.