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

Issue 685652 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
tdres...@chromium.org
█ aber...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7% regression in system_health.memory_mobile at 446025:446064

Project Member Reported by tdres...@chromium.org, Jan 26 2017 
See the link to graphs below.

Comment 1 by tdres...@chromium.org, Jan 26 2017 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 26 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors

Revision             Result                    N
chromium@446024      119461260 +- 2505492      21      good
chromium@446064      119399127 +- 2069851      21      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=load.games.lazors system_health.memory_mobile

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

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


| 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!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 26 2017

Cc: aber...@chromium.org
Owner: aber...@chromium.org

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

Hi aberent@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 : aberent
  Commit : 1b0987fa8439e011c4cbb34d640a691bccabdac4
  Date   : Wed Jan 25 09:25:49 2017
  Subject: Fetch Finch seed during restore - reland

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors
  Change       : 0.59% | 118409828.0 -> 119035069.333

Revision             Result                    N
chromium@445900      118409828 +- 1586142      14      good
chromium@445950      118603658 +- 1871177      14      good
chromium@445976      118790449 +- 1574164      14      good
chromium@445982      118677112 +- 951075       6       good
chromium@445984      118851435 +- 764065       6       good
chromium@445985      119677736 +- 809905       6       bad       <--
chromium@445988      119854319 +- 769700       6       bad
chromium@446000      119412851 +- 2317648      14      bad
chromium@446100      119035069 +- 644229       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=load.games.lazors system_health.memory_mobile

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

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


| 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!

Comment 6 by aber...@chromium.org, Jan 30 2017 

This seems highly unlikely. The code modified in this CL is only run during Chrome first run, and when Chrome's data is restored as part of setting up a new device or installing Chrome. Marking the bisect as wrong.

Comment 7 by aber...@chromium.org, Jan 30 2017

Owner: tdres...@chromium.org
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 30 2017 


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

Suspected Commit
  Author : aberent
  Commit : 1b0987fa8439e011c4cbb34d640a691bccabdac4
  Date   : Wed Jan 25 09:25:49 2017
  Subject: Fetch Finch seed during restore - reland

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_reddit
  Change       : 0.77% | 125166132.0 -> 126130592.0

Revision             Result                    N
chromium@445900      125166132 +- 1079226      9       good
chromium@445963      125572075 +- 2013385      14      good
chromium@445979      124937704 +- 1559077      6       good
chromium@445983      125925736 +- 1472237      9       good
chromium@445984      126031041 +- 1189577      9       good
chromium@445985      126836882 +- 2247313      14      bad       <--
chromium@445987      126889652 +- 1588666      9       bad
chromium@445994      126325751 +- 836448       6       bad
chromium@446025      126374291 +- 1746948      9       bad
chromium@446150      126130592 +- 1075471      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=load.news.reddit system_health.memory_mobile

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

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


| 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!
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Jan 31 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors

Revision             Result                    N
chromium@445450      119230653 +- 2563761      21      good
chromium@446150      119237662 +- 2140215      21      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=load.games.lazors system_health.memory_mobile

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

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


| 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!

Comment 12 by tdres...@chromium.org, Feb 14 2017

Owner: ----
Oops, removing myself as owner here, perf sheriffs aren't taking ownership of regressions anymore.

Comment 13 by benhenry@chromium.org, Mar 11 2017

Labels: Performance-Memory

Comment 15 by benhenry@chromium.org, Jul 27 2017

Status: WontFix (was: Untriaged)
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