New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 853005 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 853004
Owner: ----
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.2% regression in system_health.memory_mobile at 1528955187:1528964698

Project Member Reported by briander...@chromium.org, Jun 14 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 14 2018

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

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


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

health-plan-webview-phone
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 16 2018

Mergedinto: 853004
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : kylechar
  Commit : f77f6b8dba2776e23111c84c5d9333dbb03039fe
  Date   : Wed Jun 13 20:29:11 2018
  Subject: Fix UseSurfaceLayerForVideo GPU crash handling.

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background_news/background_news_nytimes
  Change       : 5.11% | 98960569.3333 -> 104019641.333

Revision                                       Result                   N
android-chrome@ca1c4e48aa                      98960569 +- 574746       6      good
android-chrome@2158fc5105                      99501583 +- 1525057      6      good
android-chrome@2158fc5105,chromium@566949      98925071 +- 684855       6      good
android-chrome@2158fc5105,chromium@566970      98811236 +- 418794       6      good
android-chrome@2158fc5105,chromium@566971      103715343 +- 347448      6      bad       <--
android-chrome@2158fc5105,chromium@566972      104625167 +- 563659      6      bad
android-chrome@2158fc5105,chromium@566973      103462073 +- 793227      6      bad
android-chrome@2158fc5105,chromium@566975      104167439 +- 751241      6      bad
android-chrome@2158fc5105,chromium@566980      103753060 +- 550840      6      bad
android-chrome@2158fc5105,chromium@566991      103609700 +- 936225      6      bad
android-chrome@f6b5646c5d                      103735993 +- 858513      6      bad
android-chrome@adcd19c5ad                      104019641 +- 323191      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=background.news.nytimes 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/8943706223664859584


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment