New issue
Advanced search Search tips

Issue 744739 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.3% regression in system_health.memory_mobile at 486714:486778

Project Member Reported by nzolghadr@chromium.org, Jul 17 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 17 2017

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

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


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 19 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_media/browse_media_imgur
  Change       : 3.32% | 63945496.0 -> 66067053.3333

Suspected Commit Range
  12 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4afd513b88234976f17b06eee24892ce9d149e7e..e5ef88bfc930b8066ae7c8a5ec5cf35577bbcd2b


Revision                           Result                   N
chromium@486713                    63945496 +- 455106       6        good
chromium@486730                    64113773 +- 1661590      6        good
chromium@486738                    63812035 +- 917489       6        good
chromium@486742                    64333251 +- 607296       6        good
chromium@486744                    64076227 +- 940234       6        good
chromium@486745                    64395715 +- 689088       6        good
chromium@486745,v8@44cce0fcc0      ---                      ---      build failure
---                                ---                      ---      too many build failures to list
chromium@486745,v8@a97abb909b      ---                      ---      build failure
chromium@486746                    66325443 +- 1381393      6        bad
chromium@486778                    66067053 +- 932043       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=browse.media.imgur 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/8973798506127834896


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
Won't be able to track down due to build failures.

Sign in to add a comment