Issue metadata
Sign in to add a comment
|
1.6%-3.7% regression in system_health.memory_mobile at 449946:450050 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8984869018926612912
,
Mar 17 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: f6ddda40e1e665606b2824f83ef63a21debde551 bad_revision : 3367918b26e434d16f477c75443389e6ec2873aa 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:malloc:effective_size_avg/background/after_http_m_youtube_com_results_q_science Revision Result N chromium@449945 31727242 +- 489293 6 good chromium@449962 31659854 +- 845090 6 good chromium@449978 33349332 +- 535319 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/8984869018926612912 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5819378722930688 | 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!
,
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 rmcilroy@chromium.org
, Mar 17 2017