New issue
Advanced search Search tips

Issue 660158 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 659168
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.8%-38.6% regression in smoothness.gpu_rasterization.top_25_smooth at 427152:427212

Project Member Reported by m...@chromium.org, Oct 27 2016

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Oct 27 2016

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

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


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

android-nexus5X
chromium-rel-win7-gpu-nvidia
Project Member

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

Mergedinto: 659168
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Initialize buffers before allowing access to them.
Author  : zmo
Commit description:
  
Also, refactor buffer access validation a bit to reduce
duplicated codes.

(Note that this is still part 1 of the work. We have more
buffer access paths that we need to put in buffer access
validation.)

BUG= 654201 
TEST=gpu_unittests, webgl_conformance
R=piman@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2435803004
Cr-Commit-Position: refs/heads/master@{#427200}
Commit  : 26c35c2e81f97a5b291ebd4d639fc3f1a4cc50e8
Date    : Tue Oct 25 01:03:34 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@427180  29.3162  0.759576  5  good
chromium@427192  29.4348  1.50462   5  good
chromium@427198  28.7436  1.38457   5  good
chromium@427199  27.074   2.34254   5  good
chromium@427200  36.2226  0.467666  5  bad    <--
chromium@427201  36.4688  0.139711  5  bad
chromium@427204  36.4831  0.221306  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 660158

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.tough_filters_cases
Test Metric: frame_times/http___rawgit.com_WebKit_webkit_master_PerformanceTests_Animometer_developer.html?test-interval_20_display_minimal_controller_fixed_frame-rate_50_kalman-process-error_1_kalman-measurement-error_4_time-measurement_performance_suite-name_Animometer_test-name_Focus_complexity_100
Relative Change: 24.45%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1940
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997615139148087088


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

| 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