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

Issue 675675 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 468240



Sign in to add a comment

8.5% regression in system_health.memory_mobile at 439095:439125

Project Member Reported by jasontiller@chromium.org, Dec 19 2016

Issue description

Not sure what to make of this graph. Odd spike, then a regression. I'll kick off a couple of bisects.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=675675

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 19 2016

Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org

=== PERF REGRESSION ===


=== 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 =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [wrapper-tracing] Reland: Turn on flag
Author  : mlippautz
Commit description:
  
BUG= chromium:468240 
NOTRY=true

Review-Url: https://codereview.chromium.org/2579043002
Cr-Commit-Position: refs/heads/master@{#439124}
Commit  : 4b81adefe8d80be06d53b33dd0d5979839596456
Date    : Fri Dec 16 16:47:01 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@439094  35630486  1216291  6  good
chromium@439110  35805440  1287632  6  good
chromium@439118  35353440  1150092  6  good
chromium@439122  35531361  1268215  6  good
chromium@439123  35758964  2310670  6  good
chromium@439124  39823986  1857821  6  bad    <--
chromium@439125  39726073  2000132  6  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 675675

Test Command: 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.cnn system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_cnn
Relative Change: 11.49%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2840
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992820422429474528


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5812777430548480

| 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!
Cc: -mlippautz@chromium.org
Components: Blink>JavaScript>GC Blink>Bindings
Status: Assigned (was: Untriaged)
Thanks, will keep that one on the radar.
Blocking: 468240
Status: Fixed (was: Assigned)
I fixed a corner case with fb8b3bcc821cf11c22593d2773c5f06823acd53f where we would not be able to keep up with the mutator and mark indefinitely, also increasing the memory footprint.

The regression seems to be fully recovered with V8 5.7.345.

Sign in to add a comment