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

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


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

android-nexus5X

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

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

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

Hi eroman@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 : eroman
  Commit : a7f495e07e33659fed8591fcabf5f3616c1042a2
  Date   : Fri May 05 02:12:35 2017
  Subject: Delete chrome://net-internals/#export

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/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 6.43% | 141903780.0 -> 150947463.556

Revision             Result                     N
chromium@469473      141903780 +- 3920057       6       good
chromium@469531      146058774 +- 11567517      9       good
chromium@469560      149374486 +- 2919436       9       good
chromium@469567      145925028 +- 10649993      6       good
chromium@469571      148976841 +- 10200151      14      good
chromium@469573      147838811 +- 17052942      21      good
chromium@469574      151213988 +- 11472600      14      bad       <--
chromium@469588      150947464 +- 2088257       9       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/8980156386720512976

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


| 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!

The identified CL cannot have been responsible for this memory change.

Back to kraynov to see if a more appropriate regression range can be found.

=== 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_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 6.15% | 144944548.0 -> 151282888.571

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/7ba3433c3a317a45c461fb499d65c7f67eecf3e7..49345d02f5e5a10cf2789d1d45b4eeec4656b542


Revision             Result                     N
chromium@469473      144944548 +- 15876540      14       good
chromium@469531      146826953 +- 14193320      14       good
chromium@469560      145070793 +- 18619399      14       good
chromium@469574      146505636 +- 12740583      14       good
chromium@469581      148629128 +- 3704825       9        good
chromium@469585      147817453 +- 13218351      14       good
chromium@469586      147072518 +- 20219505      21       good
chromium@469587      ---                        ---      build failure
chromium@469588      151282889 +- 7465273       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 memory.top_10_mobile_stress

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

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


| 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!

Seems within noise range