Disable triangulating path renderer on dmsaa
Total DMSAA Multisample Render Passes: 370 -> 220
Bug: skia:11396
Change-Id: Ibedc77a398cfe656bcb3999bd968356e221990ff
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/399841
Commit-Queue: Chris Dalton <csmartdalton@google.com>
Reviewed-by: Brian Salomon <bsalomon@google.com>
diff --git a/src/gpu/ops/GrTriangulatingPathRenderer.cpp b/src/gpu/ops/GrTriangulatingPathRenderer.cpp
index d2ae4fd..77a5e9c 100644
--- a/src/gpu/ops/GrTriangulatingPathRenderer.cpp
+++ b/src/gpu/ops/GrTriangulatingPathRenderer.cpp
@@ -195,6 +195,10 @@
GrPathRenderer::CanDrawPath
GrTriangulatingPathRenderer::onCanDrawPath(const CanDrawPathArgs& args) const {
+ // Don't use this path renderer with dynamic MSAA. DMSAA tries to not rely on caching.
+ if (args.fSurfaceProps->flags() & kDMSAA_SkSurfacePropsPrivateFlag) {
+ return CanDrawPath::kNo;
+ }
// This path renderer can draw fill styles, and can do screenspace antialiasing via a
// one-pixel coverage ramp. It can do convex and concave paths, but we'll leave the convex
// ones to simpler algorithms. We pass on paths that have styles, though they may come back
