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

Issue 641961 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 641962
Owner:
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1303.5% regression in memory.top_10_mobile at 414804:414844

Project Member Reported by mustaq@chromium.org, Aug 29 2016

Issue description

See the link to graphs below.
 

Comment 1 by mustaq@chromium.org, Aug 29 2016

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

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


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

android-nexus5X

Comment 3 by mustaq@chromium.org, Aug 29 2016

Cc: perezju@chromium.org
perezju@: most of these are huge regressions. I have kicked off several bisects, but they deserve a shortcut given the number and magnitude of regressions. Any clue might be causing these?
Cc: jasontiller@chromium.org
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 30 2016

Mergedinto: 641962
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Android: Trigger tab placeholder update when activity is paused
Author  : sievers
Commit description:
  
This makes sure we have a placeholder bitmap when we resume
and don't have a frame from the renderer yet.

BUG= 636630 

Review-Url: https://codereview.chromium.org/2186453004
Cr-Commit-Position: refs/heads/master@{#414822}
Commit  : 0a1f48d5cb6a5d263f85bc5322912b7f703c40ac
Date    : Fri Aug 26 21:50:30 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@414803  174162   182.91   5  good
chromium@414814  174162   182.91   5  good
chromium@414819  174162   182.91   5  good
chromium@414821  174162   182.91   5  good
chromium@414822  2443346  182.91   5  bad    <--
chromium@414824  2443346  182.91   5  bad
chromium@414844  2443346  182.91   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 641961

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile
Test Metric: background-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/after_http_www_baidu_com_s_word_google
Relative Change: 1302.92%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/614
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002984014076562736


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

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

Sign in to add a comment