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

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


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

android-nexus5

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

=== Auto-CCing suspected CL author nednguyen@google.com ===

Hi nednguyen@google.com, 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 : Nghia Nguyen
  Commit : 564e33d345ee080be36ad0e6b6107afbcd09df4d
  Date   : Tue Nov 07 14:06:23 2017
  Subject: Update wprgo binaries to latest version

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_news/browse_news_cnn
  Change       : 49.62% | 2308779.33333 -> 1163234.66667

Revision                                 Result                  N
chromium@515122                          2308779 +- 57436.1      6      good
chromium@515145                          2335105 +- 85444.1      6      good
chromium@515148                          2326412 +- 57143.9      6      good
chromium@515148,catapult@a7fb6add75      2342338 +- 3002.2       6      good
chromium@515148,catapult@b33d83ad5d      2319271 +- 62301.8      6      good
chromium@515148,catapult@564e33d345      1163288 +- 110.851      6      bad       <--
chromium@515148,catapult@c169bba255      1163224 +- 0.0          6      bad
chromium@515149                          1162991 +- 1457.51      6      bad
chromium@515150                          1162647 +- 2014.68      6      bad
chromium@515151                          1162980 +- 1442.03      6      bad
chromium@515156                          1162917 +- 1714.98      6      bad
chromium@515167                          1163235 +- 36.9504      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.news.cnn 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/8963288771074406624


For feedback, file a bug with component Speed>Bisection

The real change is https://chromium-review.googlesource.com/c/catapult/+/729283, which is expectedly to cause "improvement" as it describes.

 Issue 784345  has been merged into this issue.

 Issue 785729  has been merged into this issue.

 Issue 787441  has been merged into this issue.

 Issue 787415  has been merged into this issue.

 Issue 785721  has been merged into this issue.

 Issue 787449  has been merged into this issue.