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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyrSC6wkM


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

android-nexus5X

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

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

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

Hi juliatuttle@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 : juliatuttle
  Commit : aeb1abc9b5177c2817b21fe3a366fc0f23450607
  Date   : Thu May 04 21:14:38 2017
  Subject: Reporting: Plumb from //chrome/browser/browsing_data.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google
  Change       : 6.25% | 144725944.0 -> 153769400.0

Revision             Result                    N
chromium@469473      144725944 +- 869007       6      good
chromium@469474      153572621 +- 4187927      6      bad       <--
chromium@469475      150883085 +- 6616101      6      bad
chromium@469477      154036835 +- 2693959      6      bad
chromium@469481      155253347 +- 3229524      6      bad
chromium@469488      152959587 +- 9258956      6      bad
chromium@469502      157141944 +- 871577       6      bad
chromium@469531      151281592 +- 7258987      6      bad
chromium@469588      153769400 +- 2002696      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 memory.top_10_mobile_stress

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980152046799988864

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4565190286245888


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

Hi cbiesinger@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 : cbiesinger
  Commit : 047294d8a76953fb5d19b9fc20e7980f2641bc45
  Date   : Thu May 04 21:16:10 2017
  Subject: [css-flexbox] Merge align-content and justify-content handling

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google
  Change       : 5.96% | 145382498.667 -> 154054072.0

Revision             Result                     N
chromium@469473      145382499 +- 1850017       6      good
chromium@469474      148205155 +- 5207218       6      good
chromium@469475      153402637 +- 2637674       6      bad       <--
chromium@469477      152931939 +- 6601345       6      bad
chromium@469481      152046520 +- 12445556      6      bad
chromium@469488      156753165 +- 1364018       6      bad
chromium@469502      157105592 +- 1228022       6      bad
chromium@469531      154607203 +- 5509328       6      bad
chromium@469588      154054072 +- 2102473       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 memory.top_10_mobile_stress

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980152036737251632

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5301950721032192


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Extremely unlikely to be my change

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.