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

Issue 656734 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 16 days ago
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-2.1% regression in memory.top_10_mobile at 425323:425375

Project Member Reported by jasontiller@chromium.org, Oct 17 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=656734

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


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

android-nexus6
android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 17 2016

Cc: jiajia....@intel.com
Owner: jiajia....@intel.com

=== Auto-CCing suspected CL author jiajia.qin@intel.com ===

Hi jiajia.qin@intel.com, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Roll ANGLE 873d00f..336b147
Author  : jiajia.qin
Commit description:
  
https://chromium.googlesource.com/angle/angle.git/+log/873d00f..336b147

BUG= chromium:654103 , chromium:618464 ,chromium:650138

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2421873002
Cr-Commit-Position: refs/heads/master@{#425374}
Commit  : ab328c117ab17dbd4da154d8444e03b9e6631d47
Date    : Fri Oct 14 17:34:10 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@425329  1463910  2243.47  5  good
chromium@425352  1459814  2243.47  5  good
chromium@425363  1460634  2243.47  5  good
chromium@425369  1460634  2243.47  5  good
chromium@425372  1458995  1831.79  5  good
chromium@425373  1461453  1831.79  5  good
chromium@425374  1482752  0.0      5  bad    <--

Bisect job ran on: android_one_perf_bisect
Bug ID: 656734

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1716
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998531298554489408


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

| 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!
Status: WontFix (was: Untriaged)
Small ashmem changes, no further action needed.

Sign in to add a comment