Issue metadata
Sign in to add a comment
|
2.7% regression in system_health.memory_mobile at 448443:448475 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987748401375290464
,
Feb 13 2017
=== BISECT JOB RESULTS === NO Perf regression found 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/browse_news/browse_news_flipboard Revision Result N chromium@448442 21745609 +- 989222 21 good chromium@448475 21785574 +- 1495836 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 --story-filter=browse.news.flipboard system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987748401375290464 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5506834112184320 | 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!
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982612130027828352
,
Jul 27 2017
,
Jul 27 2017
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 |
|||||||||||||||||||||
Comment 1 by majidvp@google.com
, Feb 13 2017