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

Issue 714911 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Apr 2017
Cc:
█ rsch...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 718928


Sign in to add a comment

4.8% regression in memory.top_10_mobile at 466517:466537

Project Member Reported by rsch...@chromium.org, Apr 25 2017 
See the link to graphs below.

Comment 1 by rsch...@chromium.org, Apr 25 2017 

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 25 2017 


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                 N
chromium@466516      5934352 +- 457332      21      good
chromium@466537      5905793 +- 304964      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-chromium --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/8981385016519942352

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 25 2017 


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                 N
chromium@466516      5960837 +- 542045      21      good
chromium@466537      5957474 +- 499876      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-chromium --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/8981363865728052272

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


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

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 26 2017

Mergedinto: 711366
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : yosin
  Commit : e14aacd2baf5cf9c4a5e457384e0b0f73c0163c4
  Date   : Tue Apr 11 08:33:37 2017
  Subject: Get rid of computeVisibleSelectionInDOMTreeDeprecated() in InputMethodController::textInputType() and textInputInfo()

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 76.44% | 10138773.3333 -> 17888770.6667

Revision             Result                  N
chromium@462606      10138773 +- 338004      6      good
chromium@463131      10089987 +- 267216      6      good
chromium@463394      10089987 +- 267216      6      good
chromium@463525      10089987 +- 267216      6      good
chromium@463558      10089987 +- 267216      6      good
chromium@463567      10089987 +- 267216      6      good
chromium@463571      10041200 +- 0.0         6      good
chromium@463573      10041200 +- 0.0         6      good
chromium@463574      10041200 +- 0.0         6      good
chromium@463575      17888771 +- 267216      6      bad       <--
chromium@463591      17888771 +- 267216      6      bad
chromium@463656      17839984 +- 0.0         6      bad
chromium@464706      17888771 +- 267216      6      bad
chromium@466806      17888771 +- 267216      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 memory.top_10_mobile

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

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


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

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 26 2017 


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

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia: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/8981325518208546880

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


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

Comment 12 by 42576172...@developer.gserviceaccount.com, Apr 28 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                 N
chromium@466516      5960837 +- 542045      21      good
chromium@466537      5957474 +- 499876      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/8981252967973113504

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


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

Comment 13 by 42576172...@developer.gserviceaccount.com, Apr 28 2017 


=== 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: 71dc84287165f0c3f9ab02e51dbedaffb6bf680f
  bad_revision : c1b3d82ff959fb2baeb1ac8bde85da43db4e9de5

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 44.05% | 727366.666667 -> 1047785.33333

Revision             Result                  N
chromium@462606      727367 +- 25952.0       6      good
chromium@463131      724479 +- 23689.2       6      good
chromium@463394      769862 +- 290786        6      good
chromium@463525      716828 +- 306.725       6      good
chromium@463591      720315 +- 19404.0       6      good
chromium@463600      720315 +- 19404.0       6      good
chromium@463608      1046287 +- 160.665      6      bad
chromium@463624      1046299 +- 182.574      6      bad
chromium@463656      1046275 +- 227.52       6      bad
chromium@464706      1040397 +- 20461.5      6      bad
chromium@466806      1047785 +- 275.894      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 memory.top_10_mobile

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

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


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

Comment 14 by simonhatch@chromium.org, May 5 2017

Blockedon: 718928
 crbug.com/718928  for the android_webview_arm64_aosp_perf_bisect issues.
►

Sign in to add a comment