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

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


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

android-one

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_social/load_social_twitter
  Change       : 106.42% | 461880.0 -> 953400.0

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/fb1b063693e8de147a607a5400e87116508e813f..47b8f2451e900fe2c5fc4d94046925f40fea2fc7


Revision             Result                 N
chromium@523379      461880 +- 0.0          20       good
chromium@523392      461880 +- 0.0          21       good
chromium@523393      ---                    ---      build failure
chromium@523394      ---                    ---      build failure
chromium@523395      ---                    ---      build failure
chromium@523396      756792 +- 2112964      14       bad
chromium@523399      855096 +- 2849121      21       bad
chromium@523405      953400 +- 2467411      14       bad
chromium@523430      953400 +- 2467411      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=load.social.twitter 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/8960215154120625232


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149abba4840000

Trying bisect again with pinpoint.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/149abba4840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14f66026840000

Kicked another bisect because the previous one didn't produce values, but then saw that this recovered, so WontFix-ing.