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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7oy3vQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7qip8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7tKnpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgruGgpQkM


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

android-nexus6
android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/load_games/load_games_spychase

Revision             Result                    N
chromium@482272      92692677 +- 1456126       21      good
chromium@482301      92451452 +- 11720435      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=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.spychase system_health.memory_mobile

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

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


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

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

=== Auto-CCing suspected CL author sigbjornf@opera.com ===

Hi sigbjornf@opera.com, 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 : sigbjornf
  Commit : 83bd4101c86370d76a76a0e890d82ae66618f6ba
  Date   : Mon Jun 26 17:12:40 2017
  Subject: Repost offline rendering task if GC prevents.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/load_games/load_games_spychase
  Change       : 0.28% | 93102594.2857 -> 92846228.5714

Revision             Result                   N
chromium@482272      93102594 +- 7740606      14      good
chromium@482287      94347461 +- 994480       6       good
chromium@482294      94987291 +- 1134917      6       good
chromium@482298      94389332 +- 4635290      9       good
chromium@482300      94710640 +- 5197914      9       good
chromium@482301      92846229 +- 7248856      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.spychase system_health.memory_mobile

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

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


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

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

The assigned owner "sigbjornf@opera.com" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This looks like a big regression, but:
* Bisects couldn't repro (the numbers in #5 actually show a slight improvement)
* The graphs came back down a few revisions later.

WontFix-ing based on this.