New issue
Advanced search Search tips

Issue 794389 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Don't initialize GPU Raster / GrContext for UI compositor contexts

Project Member Reported by vmi...@chromium.org, Dec 13 2017

Issue description

https://codereview.chromium.org/2654993004 moved the way we blacklist GPU Raster (Ganesh) to the GPU service.

With this change we are now running LayerTreeHostImpl::UpdateGpuRasterizationStatus and LayerTreeHostImpl::GetGpuRasterizationCapabilities on the UI compositor, and initializing a skia GrContext.  The decision is made that  gpu_rasterization_enabled for UI, but it actually is never used because we never call LTHI::SetHasGpuRasterizationTrigger(true) in the UI.

We should make the decision tree clearer here, and prevent initialization of GrContext, to reduce memory and related initialization time.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Dec 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: Available (was: Untriaged)

Sign in to add a comment