Run: chrome third_party/WebKit/LayoutTests/compositing/overflow/accelerated-scrolling-with-clip-path.html --enable-gpu-rasterization --use-gl=swiftshader --enable-oop-rasterization

See: some extra clip path garbage (at least on debug linux builds).

This only appears with *both* swiftshader and oop rasterization.  The clip path appears correctly when only one (or none) is turned on.

It doesn't appear to be due to serialization of paths.  Serializing and deserializing the SkPath in the ClipPathOp constructor and then running through the gpu rasterization path in the renderer does not reproduce the problem either.

It's interesting to me that it doesn't reproduce when using gpu rasterization, because that could indicate that it's maybe an angle or command buffer workaround that's preventing the bug for gpu rasterization, as oop rasterization does not include these workarounds.

However, running with --disable-gpu-driver-bug-workarounds + gpu raster + swiftshader doesn't reproduce the bug.  It's possible that maybe there's some angle workarounds that are the problem here.

I don't know for certain if this is a swiftshader bug or a missing workaround or something else at this point.
 

Deleted: accelerated-scrolling-with-clip-path-actual.png 10.0 KB

	accelerated-scrolling-with-clip-path-actual.png 10.0 KB View Download