New issue
Advanced search Search tips

Issue 865700 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Jul 23
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 865758



Sign in to add a comment

50.6%-26214400% regression in memory.top_10_mobile at 1531967672:1531977758

Project Member Reported by npm@chromium.org, Jul 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=865700

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


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

health-plan-webview-phone

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science


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.www.google.co.uk.hl.en.q.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/8940540826038947424


For feedback, file a bug with component Speed>Bisection
Blockedon: 865758

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_search_yahoo_com_search__ylt_p_google


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=http.search.yahoo.com.search..ylt.p.google 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/8940537827676944496


For feedback, file a bug with component Speed>Bisection
Cc: enne@chromium.org
Owner: enne@chromium.org
Status: Assigned (was: Untriaged)

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

Hi enne@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 : Adrienne Walker
  Commit : f973fceec6e8eec76f90fa30d33a9a3c13aebf24
  Date   : Wed Jul 18 20:08:24 2018
  Subject: Free fewer resources when idle in oop raster

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_www_baidu_com_s_word_google
  Change       : 339.52% | 1235371.0 -> 5429675.0

Revision                                       Result              N
android-chrome@cd22f0f943                      1235371 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576157      1235371 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576174      1235371 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576178      1235371 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576179      1235371 +- 0.0      6      good
android-chrome@cd22f0f943,chromium@576180      5429675 +- 0.0      6      bad       <--
android-chrome@cd22f0f943,chromium@576182      5429675 +- 0.0      6      bad
android-chrome@cd22f0f943,chromium@576190      5429675 +- 0.0      6      bad
android-chrome@c0e3d62ff2                      5429675 +- 0.0      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=http.www.baidu.com.s.word.google 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/8940454536246043696


For feedback, file a bug with component Speed>Bisection
 Issue 865680  has been merged into this issue.
Mergedinto: 865617
Status: Duplicate (was: Assigned)

Sign in to add a comment