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

Issue 802810 link

Starred by 0 users
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
grt@chromium.org
pmonette@chromium.org
m...@chromium.org
█ jwd@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5%-1135.9% regression in system_health.memory_mobile at 529310:529347

Project Member Reported by m...@chromium.org, Jan 16 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 16 2018 

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

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


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

android-nexus5
android-nexus6
android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 17 2018 


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 1395.66% | 867701.142857 -> 8988476.57143

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ddbc1a049317170cd1e2477e0dd002ba5b6f00cb..a0cd4c1a05a431022f5ecc9ec29d505b5c216caf


Revision             Result                    N
chromium@529327      867701 +- 1493212         14       good
chromium@529328      ---                       ---      build failure
chromium@529329      ---                       ---      build failure
chromium@529330      ---                       ---      build failure
chromium@529331      11760416 +- 35951589      14       bad
chromium@529332      11759686 +- 35949221      14       bad
chromium@529338      13147121 +- 34812212      14       bad
chromium@529347      8988477 +- 35954114       14       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.shopping.avito 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/8957207164319856656


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jan 20 2018

Cc: pmonette@chromium.org jwd@chromium.org grt@chromium.org
Owner: pmonette@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ffe438840000

Add the registry key info for installed programs.
By pmonette@chromium.org · Sun Jan 14 21:43:05 2018
chromium @ 05cf9c2da24a2f4969590721bbe3ce942d13490f

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 7 by pmonette@chromium.org, Jan 22 2018

Owner: ----
Status: Available (was: Assigned)
I don't believe that the CL found with the bisect job is the right one because it is a Windows-only change.

Comment 8 by sullivan@chromium.org, Mar 16 2018

Status: WontFix (was: Available)
These all recovered.
►

Sign in to add a comment