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

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


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

health-plan-clankium-low-end-phone
health-plan-webview-phone
perf-go-phone-1024
perf-go-phone-512
perf-go-webview-phone
perf-monochrome-n-phone

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

=== Auto-CCing suspected CL author v8-autoroll@chromium.org ===

Hi v8-autoroll@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 : v8-autoroll
  Commit : 44d7d7d6b1041b57644400a00cb3fee35f6c51b2
  Date   : Tue May 22 17:44:50 2018
  Subject: Version 6.8.275

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 10.22% | 2398067.33333 -> 2643222.66667

Revision                                                     Result                  N
android-chrome@b314c993c2                                    2398067 +- 336.156      6      good
android-chrome@ab1a01d957                                    2397993 +- 747.025      6      good
android-chrome@ab1a01d957,chromium@561457                    2402761 +- 11457.0      6      good
android-chrome@ab1a01d957,chromium@561457,v8@44d7d7d6b1      2643179 +- 99.9013      6      bad       <--
android-chrome@ab1a01d957,chromium@561458                    2643188 +- 89.2995      6      bad
android-chrome@ab1a01d957,chromium@561459                    2643300 +- 221.226      6      bad
android-chrome@ab1a01d957,chromium@561463                    2643187 +- 91.0531      6      bad
android-chrome@ab1a01d957,chromium@561471                    2643114 +- 111.735      6      bad
android-chrome@ab1a01d957,chromium@561488                    2643231 +- 55.9095      6      bad
android-chrome@b1aba29374                                    2643223 +- 14.4591      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https.mobile.twitter.com.justinbieber.skip.interstitial.true 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/8945296165571798448


For feedback, file a bug with component Speed>Bisection

 Issue 847161  has been merged into this issue.

 Issue 847160  has been merged into this issue.

Recovered