Open
Bug 1193432
Opened 9 years ago
Updated 2 years ago
Lazily copy layers::Image data into WebGL textures
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P5)
Tracking
()
NEW
People
(Reporter: mattwoodrow, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Generally when we use glTexImage2D with a video element, we only ever want to read from the texture. In this case we can probably just use the original image directly (if it can be directly bound to a texture) until someone tries a write operation and then do the copy at that point. On OSX at least, copying 4k video frames into WebGL is very expensive and skipping it would be a big win.
Reporter | ||
Comment 1•9 years ago
|
||
Actually, we probably can't do this for OSX since the source texture is YUV. It'll be a win on windows with DXVA though where we have RGB textures.
Updated•9 years ago
|
Whiteboard: [gfx-noted]
Updated•5 years ago
|
Type: defect → enhancement
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•