Issue metadata
Sign in to add a comment
|
4.2%-100% regression in memory.top_10_mobile at 482319:482363 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 29 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : kenrb Commit : 00d432064a6fcd6252211a938840efb8e36b463f Date : Mon Jun 26 18:37:11 2017 Subject: Make AreCrossProcessFramesPossible return true on Android Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html Change : 100.00% | 65536.0 -> 131072.0 Revision Result N chromium@482332 65536.0 +- 0.0 6 good chromium@482333 131072 +- 0.0 6 bad <-- chromium@482334 131072 +- 0.0 6 bad chromium@482336 131072 +- 0.0 6 bad chromium@482340 131072 +- 0.0 6 bad chromium@482348 131072 +- 0.0 6 bad chromium@482363 131072 +- 0.0 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/8975548616884183152 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5977805642268672 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 28 2017