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

Issue 659539 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

7.8% regression in thread_times.key_mobile_sites_smooth at 427134:427212

Project Member Reported by alexclarke@chromium.org, Oct 26 2016

Issue description

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 26 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@427133  2.19636  0.0517089  5  good
chromium@427173  2.15728  0.0275471  5  good
chromium@427193  2.12929  0.0269411  5  good
chromium@427198  2.16688  0.0274418  5  good
chromium@427199  2.1664   0.05217    5  good
chromium@427200  2.39779  0.0302212  5  bad    <--
chromium@427201  2.38971  0.0319071  5  bad
chromium@427203  2.3916   0.0314125  5  bad
chromium@427212  2.36501  0.0575403  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 659539

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_mobile_sites_smooth
Test Metric: thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
Relative Change: 7.68%
Score: 99.9

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


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

| 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