Issue metadata
Sign in to add a comment
|
1.8%-28069.6% regression in system_health.memory_mobile at 403829:403961 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 15 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007060716674145856
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006395364099263984
,
Jul 23 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Activate complex text path on Android Author : drott Commit description: In Chromium commit 10749067720a341 catapult was rolled, switching to default teardowns between pageset repeats, compare [1]. Activating complex text on Android again after this change in order to see how measurements are affected by this. If no memory regression shows up in the memory health measurements for memory pagesets this would indicate that we may have a memory-leakage over time problem in webview single-process mode but no issues in the usual tab process lifecycle on Android. Activating and TBR'ing to collect bot results, potentially reverting later if needed for further investigation. [1] https://github.com/catapult-project/catapult/issues/2294 BUG=577306 TBR=eae Review-Url: https://codereview.chromium.org/2123653005 Cr-Commit-Position: refs/heads/master@{#403884} Commit : 5009e3effbb04c74140d262fb71bc51cbf38913a Date : Wed Jul 06 11:39:32 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@403820 972.0 0.0 5 good chromium@403856 972.0 0.0 5 good chromium@403874 972.0 0.0 5 good chromium@403883 972.0 0.0 5 good chromium@403884 38264.0 0.0 5 bad <-- chromium@403885 38264.0 0.0 5 bad chromium@403887 38264.0 0.0 5 bad chromium@403891 38264.0 0.0 5 bad chromium@403961 38264.0 0.0 5 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 628635 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:font_caches:effective_size_avg/load_search_google Relative Change: 3836.63% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/823 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006395364099263984 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5215537890590720 | 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 Tests>AutoBisect. Thank you!
,
Aug 30 2016
,
Aug 30 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 15 2016