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

Issue 611448 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 611449
Owner:
Last visit 27 days ago
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1% regression in thread_times.tough_scrolling_cases at 393081:393111

Project Member Reported by pras...@chromium.org, May 12 2016

Issue description

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

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


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

linux-release
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, May 12 2016

Mergedinto: 611449
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Fix paint invalidation rect of LayoutView
Author  : wangxianzhu
Commit description:
  
The bug was caused by http://crrev.com/1929413002 which uses
selfVisualOverflowRect() instead of visualOverflowRect() to calculate
paint invalidation rect. It caused wrong paint invalidation rect
for LayoutView.

Before rootLayerScrolls is launched, LayoutView's overflow model is
special. We should calculate its paint invalidation rect based on its
special visualOverflowRect() for now.

BUG= 611046 

Review-Url: https://codereview.chromium.org/1971843002
Cr-Commit-Position: refs/heads/master@{#393099}
Commit  : c053f70ee05c2dd91bf8b9da324e2a631e356bdc
Date    : Wed May 11 23:13:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@393080  11.354   0.204434   5  good
chromium@393096  11.4592  0.126553   5  good
chromium@393098  11.2653  0.101031   5  good
chromium@393099  11.9124  0.12524    5  bad    <--
chromium@393100  12.1559  0.0216225  5  bad
chromium@393104  11.9591  0.217155   5  bad
chromium@393111  11.9278  0.144333   5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 611448

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases
Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
Relative Change: 5.05%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6491
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012850172974235888


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

| 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