222268 2021-02-22 06:46:52 -0800 Videos do not work as sources for WebGL TexImage calls in SW fallback case in GPU Process 2021-02-26 16:04:46 -0800 1 1 1 Unclassified WebKit Media Other Unspecified Unspecified RESOLVED DUPLICATE 222461 https://bugs.webkit.org/show_bug.cgi?id=222461 InRadar P2 Normal --- 217211 221838 1 kkinnunen webkit-unassigned jer.noble peng.liu6 simon.fraser webkit-bug-importer oldest_to_newest 1732113 0 kkinnunen 2021-02-22 06:46:52 -0800 Videos do not work as sources for WebGL TexImage calls in SW fallback case in GPU Process void MediaPlayerPrivateRemote::paintCurrentFrameInContext(GraphicsContext&, const FloatRect&) { notImplemented(); } 1732115 1 kkinnunen 2021-02-22 06:53:32 -0800 Options to fix: 1) Implement readback in MediaPlayerPrivateRemote::paintCurrentFrameInContext 2) Move the ImageBuffer -> Texture logic from WebGLRenderingContextBase to GraphicsContextGL 2 is better long term 1733009 2 webkit-bug-importer 2021-02-24 11:59:29 -0800 <rdar://problem/74706834> 1733017 3 kkinnunen 2021-02-24 12:12:43 -0800 For option 2: The work is to convert void WebGLRenderingContextBase::texImageImpl(TexImageFunctionID functionID, GCGLenum target, GCGLint level, GCGLenum internalformat, GCGLint xoffset, GCGLint yoffset, GCGLint zoffset, GCGLenum format, GCGLenum type, Image* image, GraphicsContextGL::DOMSource domSource, bool flipY, bool premultiplyAlpha, bool ignoreNativeImageAlphaPremultiplication, const IntRect& sourceImageRect, GCGLsizei depth, GCGLint unpackImageHeight) to run on GPU process side resources. Essentially converting Image* image to GPU process side resource. However, that function _also_ needs to stay mostly working with Web process side resources, since some of the cases are such that probably no reasonable GPU process side resource exist. 1733979 4 jer.noble 2021-02-26 14:31:18 -0800 This was likely fixed by r273568, which will pull images across the process boundary when painting/texturing occurs there. 1734053 5 peng.liu6 2021-02-26 16:04:46 -0800 *** This bug has been marked as a duplicate of bug 222461 ***