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

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


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

android-nexus5
android-one
chromium-rel-mac12

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

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_nytimes

Revision             Result                   N
chromium@506714      47465666 +- 1526583      21      good
chromium@506807      47654634 +- 1111612      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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966181816908666256


For feedback, file a bug with component Speed>Bisection

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

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

Hi lpy@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 : Peiyong Lin
  Commit : 6161e912bd613a6487e12410344cff99ba994db4
  Date   : Thu Oct 05 17:10:25 2017
  Subject: Merge network idleness signal with Performance Monitor.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
  Change       : 1.29% | 13049793.1429 -> 13218095.4286

Revision             Result                  N
chromium@506720      13049793 +- 477617      14      good
chromium@506755      13011692 +- 241603      6       good
chromium@506772      13017318 +- 254760      9       good
chromium@506773      13211678 +- 258525      9       bad       <--
chromium@506774      13270762 +- 250821      6       bad
chromium@506775      13315351 +- 321109      6       bad
chromium@506777      13227747 +- 224164      6       bad
chromium@506781      13251329 +- 317622      9       bad
chromium@506789      13209210 +- 375144      21      bad
chromium@506857      13218095 +- 347310      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=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966098129420749808


For feedback, file a bug with component Speed>Bisection

 Issue 775662  has been merged into this issue.