Bug 2038906 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)
> Does Chrome have something similar?

chromium allocates IDCompositionTexture in D3DImageBacking. It is triggered by [D3DImageBackingFactory::CreateSharedImage()](https://source.chromium.org/chromium/chromium/src/+/main:gpu/command_buffer/service/shared_image/d3d_image_backing_factory.cc;l=725;drc=d8351b27618c83eb94491b3b6bbfbc341a640001).

chromium does not have a code to disable overlay like [D299978](https://phabricator.services.mozilla.com/D299978). chromium seems not have a problem like Bug 2036365. Since D3DImageBacking seems always recycled.
Revision 1 by
on 
(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)
> Does Chrome have something similar?

chromium allocates IDCompositionTexture in D3DImageBacking. It is triggered by [D3DImageBackingFactory::CreateSharedImage()](https://source.chromium.org/chromium/chromium/src/+/main:gpu/command_buffer/service/shared_image/d3d_image_backing_factory.cc;l=725;drc=d8351b27618c83eb94491b3b6bbfbc341a640001).

chromium does not have a code to disable overlay like [D299978](https://phabricator.services.mozilla.com/D299978). chromium seems not have a problem like Bug 2036365. Since D3DImageBacking seems always recycled.

Bug 2036655 is going to recycle DXGITextureHostD3D11 for WebGPU and WebGL.

Back to Bug 2038906 Comment 4