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

Issue 794972 link

Starred by 1 user
Status: Duplicate
Merged: issue 794973
Owner:
█ ethannicholas@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
█ kraynov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

117.7%-211.8% regression in smoothness.tough_path_rendering_cases at 523432:523585

Project Member Reported by kraynov@chromium.org, Dec 14 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 14 2017 

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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-pro

Comment 3 by sullivan@chromium.org, Jan 23 2018 

Kicking another bisect.

Comment 6 by sullivan@chromium.org, Jan 29 2018

Owner: ethannicholas@chromium.org
Status: Assigned (was: Untriaged)
ethannicholas: Sorry for the late notice again. The bisector isn't updating the bug, but if you look at the links in #2, #4, and #5 it's pretty clear your CL, "converted vertex shaders to device coords" regressed this benchmark. Can you take a look?

Comment 7 by sullivan@chromium.org, Jan 29 2018 

 Issue 794979  has been merged into this issue.

Comment 8 by sullivan@chromium.org, Jan 29 2018 

Duping in some more regressions with same notification issue from  bug 794889 .

Comment 9 by vmi...@chromium.org, Feb 5 2018

Components: Internals>GPU>Metrics

Comment 10 by senorblanco@chromium.org, May 1 2018 

ethannicolas@: friendly ping.

Comment 11 by ethannicholas@chromium.org, May 8 2018

Mergedinto: 794973
Status: Duplicate (was: Assigned)
►

Sign in to add a comment