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

Issue 692968 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

1.2% regression in system_health.memory_mobile at 448787:448822

Project Member Reported by alexclarke@chromium.org, Feb 16 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2IekvQsM


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 17 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_chrome:v8:effective_size_avg/load_news/load_news_hackernews
  Change       : 0.52% | 2723704.0 -> 2737914.66667

Suspected Commit Range
  10 commits in range
  https://chromium.googlesource.com/chromium/src/+log/b45a817c9a86d2d25ed6fba359abceafc728c2d3..9aad3ae4ce41aeec08f59af3536d72ec79f5a641


Revision                           Result                  N
chromium@448786                    2723704 +- 0.0          6        good
chromium@448804                    2723656 +- 262.907      6        good
chromium@448813                    2723693 +- 36.9504      6        good
chromium@448814                    2723656 +- 262.907      6        good
chromium@448814,v8@17c2dd3886      ---                     ---      build failure
chromium@448814,v8@4d8bde0cd6      ---                     ---      build failure
chromium@448814,v8@c205c9b7ea      ---                     ---      build failure
chromium@448814,v8@878a3df75e      ---                     ---      build failure
chromium@448814,v8@de700757ff      ---                     ---      build failure
chromium@448814,v8@04568c5216      ---                     ---      build failure
chromium@448814,v8@d0bccc9c6a      ---                     ---      build failure
chromium@448814,v8@f6a325fb01      ---                     ---      build failure
chromium@448814,v8@5cc3c0353e      ---                     ---      build failure
chromium@448815                    2738155 +- 1420.84      6        bad
chromium@448816                    2737920 +- 0.0          6        bad
chromium@448818                    2737920 +- 0.0          6        bad
chromium@448822                    2737915 +- 29.2119      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=load.news.hackernews system_health.memory_mobile

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

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


| 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!
Labels: Performance-Memory
Status: WontFix (was: Untriaged)
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.

Sign in to add a comment