In directly composited case, allow direct use of cached CC Cached GPU Images for tiles |
||||
Issue descriptionWhen dealing with directly composited images, where a single image is assigned to a layer, we still: a) Decode the image into our CC image decode cache b) Upload the image to the GPU c) Raster the uploaded image into a tile (basically a copy) d) Draw the tile (b) and (c) can be collapsed, as we're basically generating two GPU copies of the same texture. An approach that might solve this is: 1) Hand off the uploaded texture from (b) in a texture mailbox, and have the compositor use that directly. This is probably the most "correct" solution, allowing the image to be cached as normal. The complexity here is that the cache can now have permanently vended out images.
,
Jul 28 2017
ericrk, can you find an owner for this or downgrade to p2?
,
Aug 29 2017
Downgrading to p2. If you feel like this should still be a p1, please find an owner for it.
,
Aug 30
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 30
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ericrk@chromium.org
, Jul 10 2017Labels: -Type-Bug Type-Feature