New issue
Advanced search Search tips

Issue 661502 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

1.9% regression in memory.top_10_mobile at 428225:428292

Project Member Reported by primiano@chromium.org, Nov 2 2016

Issue description

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

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


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

android-nexus6
Mergedinto: 660562
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Remove runtime flag 'UnsafeES3APIs' from blink webgl.
Author  : yunchao.he
Commit description:
  
This is the first step to remove unsafe mode and enable
ES3 APIs for WebGL2 and ES3 context by default.
Command line option "--enable-unsafe-es3-apis" would be
unnecessary and removed afterwards.

Intent to implement:
https://www.chromestatus.com/features/6694359164518400

Launch bug:
http://crbug.com/641635
(Note that this is not the launch CL -- it's still not possible to create a WebGL 2.0 context without the flag)

BUG= 654787 , 641635
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2451943002
Cr-Commit-Position: refs/heads/master@{#428253}
Commit  : 58dd74648c572ceaf28175b2a2802d3c50a9b316
Date    : Fri Oct 28 02:27:13 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@428224  1139200  6359.64  8   good
chromium@428241  1145515  6282.98  18  good
chromium@428250  1147790  7564.03  27  good
chromium@428252  1148778  7989.7   41  good
chromium@428253  1149577  5149.39  41  bad    <--
chromium@428254  1152796  6256.74  27  bad
chromium@428258  1150976  6050.19  12  bad
chromium@428292  1153024  6568.21  8   bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 661502

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_m_intl_taobao_com_group_purchase_html
Relative Change: 0.65%
Score: 95.0

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


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

| 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