New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 853003 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.2% regression in system_health.memory_mobile at 1528887793:1528899648

Project Member Reported by briander...@chromium.org, Jun 14 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 14 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=853003

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3cd548a55b21161af8d795075c3b1239e5bec1adaf3fda546930c8fda7b91c41


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

perf-go-phone-512
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 15 2018

Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author mlippautz@chromium.org ===

Hi mlippautz@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Michael Lippautz
  Commit : aceb7d670d0cca38d219cadfc529390c755c299c
  Date   : Mon Jun 11 11:40:36 2018
  Subject: [oilpan] Fix for EsimateLiveSize

Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_cnn
  Change       : 3.57% | 95496192.0 -> 98905201.7778

Revision                                       Result                   N
android-chrome@cd18451841                      95496192 +- 1484578      14      good
android-chrome@cd18451841,chromium@565955      94808942 +- 1281664      14      good
android-chrome@cd18451841,chromium@565962      93945173 +- 1092818      6       good
android-chrome@cd18451841,chromium@565965      94630571 +- 1179976      6       good
android-chrome@cd18451841,chromium@565966      94607360 +- 1560417      6       good
android-chrome@cd18451841,chromium@565967      97141029 +- 2331547      14      bad       <--
android-chrome@cd18451841,chromium@565991      97539413 +- 1456294      9       bad
android-chrome@cd18451841,chromium@566038      97480021 +- 914582       6       bad
android-chrome@cd18451841,chromium@566135      98762459 +- 2691691      14      bad
android-chrome@cd18451841,chromium@566328      99050837 +- 1721351      6       bad
android-chrome@b1b15efc34                      98805760 +- 2428167      6       bad
android-chrome@9cd870ee9e                      98905202 +- 3415406      9       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn 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/8943706250983195264


For feedback, file a bug with component Speed>Bisection
Cc: -mlippautz@chromium.org haraken@chromium.org
Components: Blink>MemoryAllocator>GarbageCollection
Status: Fixed (was: Assigned)
CL has been reverted.

Sign in to add a comment