New issue
Advanced search Search tips

Issue 718032 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 716390
Owner: ----
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.3% regression in system_health.memory_mobile at 467308:467448

Project Member Reported by mustaq@chromium.org, May 3 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=718032

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0qnapQoM


Bot(s) for this bug's original alert(s):

android-one
Mergedinto: 716390
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ben
  Commit : b932d5ad0c349295c9d10de144f9358370e57b5c
  Date   : Wed Apr 26 19:40:13 2017
  Subject: Implement Connector::ApplySpec() & use to enforce navigation:frame.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_cnn
  Change       : 8.04% | 21127415.6667 -> 22825568.6667

Revision             Result                  N
chromium@467307      21127416 +- 832952      6      good
chromium@467378      21254044 +- 300415      6      good
chromium@467413      21167971 +- 244991      6      good
chromium@467414      21216111 +- 333004      6      good
chromium@467415      22781123 +- 376158      6      bad       <--
chromium@467416      23037053 +- 281729      6      bad
chromium@467418      22938566 +- 923906      6      bad
chromium@467422      22847295 +- 160339      6      bad
chromium@467431      22842004 +- 299565      6      bad
chromium@467448      22825569 +- 505119      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980604889532497792

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6441634067120128


| 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