New issue
Advanced search Search tips

Issue 846078 link

Starred by 2 users
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: May 2018
Cc:
sunyunjia@chromium.org
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-7.8% regression in system_health.common_desktop at 558219:560066

Project Member Reported by sunyunjia@chromium.org, May 23 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 23 2018 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=8ee5e69b5b01e12cdf9559d8efb861ad6f9ce6192cd39f108aa50421099e75c0


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

chromium-rel-mac11-pro
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 24 2018

Cc: chrishtr@chromium.org
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12b85e5c240000

Apply fixed-position scroll offset if the containing block is ancestor. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/edc066c316b24fb3dea226ae6c1c5c1fdee062c3

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by chrishtr@chromium.org, May 24 2018

Status: WontFix (was: Assigned)
This is just reverting back to normal.
►

Sign in to add a comment