[Win] Can ask for a bitmap that is too large when accelerated compositing and tiling

• Component: Layout and Rendering
• Status: RESOLVED CONFIGURATION CHANGED

[Chris Marrin]

When running compositing/tiling/huge-layer-with-layer-children.html we ask for a bitmap that is 500 by 20000, which is too large and the creation fails. This hits an assert in GraphicsContextCGWin::CGContextWithHDC because bmBitsPixel is zero. But this seems benign, so for now I added a graceful exit rather than the assert. But we should understand why we're going down this path.

[Ahmad Saleem]

(In reply to Chris Marrin from comment #0)
> When running compositing/tiling/huge-layer-with-layer-children.html we ask
> for a bitmap that is 500 by 20000, which is too large and the creation
> fails. This hits an assert in GraphicsContextCGWin::CGContextWithHDC because
> bmBitsPixel is zero. But this seems benign, so for now I added a graceful
> exit rather than the assert. But we should understand why we're going down
> this path.

This test seems to be only marked as 'Failure' on GTK and 'Skip' for wincairo build and it does not seems to be an issue on mac systems.

While I couldn't find - GraphicsContextCGWin or CGContextWithHDC in WebKit source (might have been renamed etc.).

From the 'Hardware' field, it seems that it was 'Windows' bit so don't know whether wincairo would be still applicable or since Apple Windows build is gone, this is no longer applicable.

Just wanted to share latest status to see if we can close this or we still need to do something here for 'wincairo' builds.

[Fujii Hironori]

AppleWin port was removed. I confirmed WinCairo port doesn't have the problem for the test.