Bug 222101 – HTMLCanvasElement::copiedImage() contains old image with GPU Process on

• Status: RESOLVED
• Resolution: FIXED
• Component: Canvas

[Kimmo Kinnunen]

HTMLCanvasElement::copiedImage() contains old image with GPU Process on

LayoutTests/fast/canvas/webgl/canvas-2d-webgl-texture.html appears to fail because HTMLCanvasElement::copiedImage() returns a new Image that contains old data.

The test is roughly as follows:
  ctx.fillStyle = "rgb(200, 0, 0)";
  ctx.fillRect(0, 0, 256, 256);
  gl.texImage2D(gl.TEXTURE_2D, 0, gl.RGBA, gl.RGBA, gl.UNSIGNED_BYTE, canvas2d); // Calls HTMLCanvasElement::copiedImage() 

  ctx.fillStyle = "rgb(0, 0, 200)";
  ctx.fillRect(0, 0, 256, 256);
  gl.texImage2D(gl.TEXTURE_2D, 0, gl.RGBA, gl.RGBA, gl.UNSIGNED_BYTE, canvas2d); // Calls HTMLCanvasElement::copiedImage()

It appears that while the second copiedImage should contain the blue contents, it still contains the red contents.

The copy is done with:

RefPtr<NativeImage> ImageBufferCGBitmapBackend::copyNativeImage(BackingStoreCopy copyBehavior) const
{
    switch (copyBehavior) {
    case CopyBackingStore:
        return NativeImage::create(adoptCF(CGBitmapContextCreateImage(context().platformContext())));

[Kimmo Kinnunen]

Said, do you have idea is the ConcreteImageBuffer::copyImage supposed to work?

Why RemoteImageBufferProxy::getImageData() has to ask the data from GPU Process
while RemoteImageBufferProxy::copyImage() can access the shared memory region in Web Process?

[Kimmo Kinnunen]

Created attachment 421180 [details]
Patch

[Kimmo Kinnunen]

Created attachment 421185 [details]
Patch

[Simon Fraser (smfr)]

Comment on attachment 421185 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=421185&action=review

> Source/WebKit/GPUProcess/graphics/RemoteRenderingBackend.cpp:350
> +void RemoteRenderingBackend::getShareableBitmapForImageBuffer(WebCore::RenderingResourceIdentifier identifier, WebCore::PreserveResolution preserveResolution, CompletionHandler<void(ShareableBitmap::Handle&&)>&& completionHandler)

Does this need to use a CompletionHandler, since it's synchronous?

[Kimmo Kinnunen]

(In reply to Simon Fraser (smfr) from comment #4)
> Comment on attachment 421185 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=421185&action=review
> 
> > Source/WebKit/GPUProcess/graphics/RemoteRenderingBackend.cpp:350
> > +void RemoteRenderingBackend::getShareableBitmapForImageBuffer(WebCore::RenderingResourceIdentifier identifier, WebCore::PreserveResolution preserveResolution, CompletionHandler<void(ShareableBitmap::Handle&&)>&& completionHandler)
> 
> Does this need to use a CompletionHandler, since it's synchronous?

I think it needs the CompletionHandler since it is processing a message that has a result. E.g. both async and sync messages post replies with CompletionHandler.
 
Yeah, all get*ForImageBuffer are synchronous, including this getShareableBitmapForImageBuffer().

[EWS]

Committed r273301: <https://commits.webkit.org/r273301>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 421185 [details].

[Radar WebKit Bug Importer]

<rdar://problem/74633005>

[Said Abou-Hallawa]

*** Bug 220553 has been marked as a duplicate of this bug. ***