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

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


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

android-nexus5X
android-webview-nexus6

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

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

Hi jkummerow@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 : Jakob Kummerow
  Commit : cfcdeab0028b7f27fff277adfef602776aeeb37b
  Date   : Tue Sep 05 18:00:39 2017
  Subject: [storeic] Drop duplicate stubs for each LanguageMode

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 16.18% | 7597114.66667 -> 8826197.33333

Revision                           Result                  N
chromium@499616                    7597115 +- 99080.4      6      good
chromium@499747                    7673901 +- 397800       6      good
chromium@499812                    7632071 +- 204021       6      good
chromium@499813                    7604302 +- 223823       6      good
chromium@499813,v8@fbd1d1ad25      7580158 +- 76185.2      6      good
chromium@499813,v8@62fee3b64c      7655677 +- 194831       6      good
chromium@499813,v8@cfcdeab002      8778349 +- 124024       6      bad       <--
chromium@499813,v8@1400544c37      8849460 +- 257874       6      bad
chromium@499814                    8832819 +- 200798       6      bad
chromium@499815                    8846124 +- 200218       6      bad
chromium@499817                    8804001 +- 164131       6      bad
chromium@499821                    8755315 +- 139433       6      bad
chromium@499829                    8781620 +- 234763       6      bad
chromium@499845                    8828407 +- 260208       6      bad
chromium@499877                    8826197 +- 181028       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=browse.news.washingtonpost 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/8965358973833414256


For feedback, file a bug with component Speed>Bisection

This doesn't make any sense; that CL reduced memory consumption.

My guess: reduced memory consumption triggers GC later, causing *average* memory over the course of the benchmark to go up.

Feel free to reassign this if you think the blame-result is not trustworthy. Otherwise there's definitely nothing to be done here.

cc-ing test owner perezju to see if he wants to reopen investigation.