This happens only when run as a layout test.
It appears that RuntimeEnabledFeatures::experimentalCanvasFeaturesEnabled() is being set to true in this layout test.
When we elide this CanvasRenderingContext::CanvasRenderingContext, the issue goes away.
There is a lot of code behind
if (RuntimeEnabledFeatures::experimentalCanvasFeaturesEnabled() &&
RuntimeEnabledFeatures::colorCorrectRenderingEnabled())
which is causing these bugs.
IMO we should add a --enable-canvas-color-modes, or something to that effect.
As it is, we need to keep this stuff disabled as we enable color correct rendering.
I can repro most of these failures with the full command line
--disable-gpu-rasterization \
--enable-color-correct-rendering \
--force-color-profile=srgb \
--enable-experimental-canvas-features \
--diasble-zero-copy \
Comment 1 by ccameron@chromium.org
, May 20 2017There is a lot of code behind if (RuntimeEnabledFeatures::experimentalCanvasFeaturesEnabled() && RuntimeEnabledFeatures::colorCorrectRenderingEnabled()) which is causing these bugs. IMO we should add a --enable-canvas-color-modes, or something to that effect. As it is, we need to keep this stuff disabled as we enable color correct rendering. I can repro most of these failures with the full command line --disable-gpu-rasterization \ --enable-color-correct-rendering \ --force-color-profile=srgb \ --enable-experimental-canvas-features \ --diasble-zero-copy \