New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 806133 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocked on:
issue 768108



Sign in to add a comment

Use CHROMIUM_texture_storage_image in WebGL's DrawingBuffer

Project Member Reported by kbr@chromium.org, Jan 26 2018

Issue description

In  Issue 768108  a new CHROMIUM_texture_storage_image extension was added which allocates GpuMemoryBuffers on the GPU service side. WebGL's DrawingBuffer should be switched to use this extension rather than its current allocation path (CreateImageCHROMIUM / BindTexImage2DCHROMIUM). The only reason to use that path is if CPU-side rendering is going to be done into the GpuMemoryBuffer, which WebGL doesn't.

(CC'ing junov@ and xlai@ in case a similar optimization is possible for 2D canvas.)

 

Comment 1 by junov@chromium.org, Jan 27 2018

As a matter of fact, Canvas 2D can benefit.  I will create a crbug for it.  Thx.

Comment 2 Deleted

Cc: -junov@chromium.org

Sign in to add a comment