Regression in browser_process:reported_by_chrome:malloc:effective_size_avg load_news_reddit on android-one |
||
Issue description
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:browser_process:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_reddit 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 --story-filter=load.news.reddit system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8973090305859789488 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
Bisect can't repro. |
||
►
Sign in to add a comment |
||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 25 2017