New issue
Advanced search Search tips

Issue 852738 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.5%-5.5% regression in smoothness.gpu_rasterization.tough_path_rendering_cases at 565880:565892

Project Member Reported by mvstanton@google.com, Jun 14 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 14 2018

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

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


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

android-nexus5X
android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 14 2018

Cc: senorblanco@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16c431f9240000

GrTessellator: catch missing intersections. by senorblanco@chromium.org
https://skia.googlesource.com/skia/+/89042d5f13a56d6b663657aa58f17593123a344e
99.52 → 104.2 (+4.671)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Sadly, this is expected. See the last line of the commit: "This extra check may result in a performance hit, so we'll have to watch the perf bots carefully."

I'll keep this bug open to see if there's a way we can recoup it, but we need this change for correctness.
Owner: senorblanco@chromium.org

Sign in to add a comment