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

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


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

android-nexus5X
android-nexus6
android-nexus7v2

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

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

Hi xunjieli@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 : xunjieli
  Commit : 357e1deefca78c61e457f340270c9cd6f38321f5
  Date   : Thu Aug 03 22:16:30 2017
  Subject: [wpr-go] Use a dummy cert if no cert is recorded

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_tools/load_tools_weather
  Change       : 878.24% | 2129308.0 -> 20829651.3333

Revision                                 Result                  N
chromium@491858                          2129308 +- 0.0          6      good
chromium@491912                          2129308 +- 0.0          6      good
chromium@491919                          2129308 +- 0.0          6      good
chromium@491923                          2129308 +- 0.0          6      good
chromium@491924                          2129308 +- 0.0          6      good
chromium@491924,catapult@b0f1e24d46      2129308 +- 0.0          6      good
chromium@491924,catapult@357e1deefc      21130145 +- 482774      6      bad       <--
chromium@491925                          20874211 +- 422247      6      bad
chromium@491926                          20934291 +- 385162      6      bad
chromium@491939                          20948284 +- 415710      6      bad
chromium@491965                          20829651 +- 361980      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=load.tools.weather 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/8971934191837457888


For feedback, file a bug with component Speed>Bisection

I assume the bisect result is invalid, unassigning.

Thanks jgruber@. The bisect is correct. 357e1deefca78c61e457f340270c9cd6f38321f5 fixed an issue where some pages were loading incompletely after wprgo migration (r489923). Because pages were loading incompletely, some memory metrics "improved". I see that these memory metrics have gone back to their original values before r489923, so I am applying WontFix here.

Issue 752864 has been merged into this issue.

 Issue 753276  has been merged into this issue.

 Issue 753650  has been merged into this issue.

 Issue 753822  has been merged into this issue.

 Issue 753827  has been merged into this issue.

 Issue 753991  has been merged into this issue.

 Issue 754631  has been merged into this issue.