New issue
Advanced search Search tips

Issue 729225 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 728293



Sign in to add a comment

4% regression in memory.top_10_mobile at 476294:476329

Project Member Reported by m...@chromium.org, Jun 2 2017

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Jun 2 2017

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

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


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

android-webview-nexus6

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_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


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 memory.top_10_mobile

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

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


| 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!

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_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

Revision             Result                 N
chromium@476293      4263836 +- 535749      21      good
chromium@476329      4244332 +- 506985      21      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 memory.top_10_mobile

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

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


| 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!

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 6281b70b9a36a64590f99c799ee55264da6cb52d
  bad_revision : df421e877181f53cf6e5aeb1611f88766efc3f5c

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_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       : 2.84% | 4139411.14286 -> 4257106.85714

Revision             Result                  N
chromium@476242      4139411 +- 57591.3      14      good
chromium@476337      4324230 +- 270924       6       bad
chromium@476432      4257107 +- 451928       14      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 memory.top_10_mobile

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

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


| 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!
Blockedon: 728293
Blocking on crbug.com/728293 for the failure.

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 6281b70b9a36a64590f99c799ee55264da6cb52d
  bad_revision : d78c189fb8e7d5792fd53a91f64c6a158b0f510a

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_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       : 2.86% | 4141028.57143 -> 4259444.38095

Revision             Result                 N
chromium@476242      4141029 +- 125540      21      good
chromium@476290      4315792 +- 290506      6       bad
chromium@476337      4237272 +- 424445      14      bad
chromium@476432      4259444 +- 566786      21      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 memory.top_10_mobile

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

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


| 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!
Status: WontFix (was: Untriaged)
We've updated the alerting configs to ignore regressions < 128kib, and these are smaller than that.

Sign in to add a comment