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

Issue 893378 link

Starred by 3 users
Status: Fixed
Owner:
dcasta...@chromium.org
Closed: Nov 5
Cc:
█ marc...@chromium.org
ccameron@chromium.org
osh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Enable GPU raster for ChromeOS UI.

Project Member Reported by dcasta...@chromium.org, Oct 9 
ChromeOS UI is currently using single threaded SW raster.
With the latest launcher window, OneCopyRasterBuffer::Playback can easily take more than 50ms.

Enabling GPU raster we can reduce the CPU time moving work to the GPU.

This issue is to keep track of enabling GPU raster, that should be as easy as crrev.com/c/1270215 at this point, and to deal with possible regressions.
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 10 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0ab7e22340d7add8786a53a14577faa5c262ced0

commit 0ab7e22340d7add8786a53a14577faa5c262ced0
Author: Daniele Castagna <dcastagna@chromium.org>
Date: Wed Oct 10 22:41:03 2018

cros: Enable GPU raster for UI

Bug:  893378 
Test: 'start ui' on a device with non-blacklisted GPU raster
Change-Id: I8cddfd282037328299be9b5206b061319aa3ed0d
Reviewed-on: https://chromium-review.googlesource.com/c/1270215
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598549}
[modify] https://crrev.com/0ab7e22340d7add8786a53a14577faa5c262ced0/ui/base/ui_base_features.cc

Comment 2 by tbuckley@google.com, Oct 12

Components: Internals>Compositing

Comment 3 by enne@chromium.org, Oct 12

Status: Assigned (was: Untriaged)

Comment 4 by dcasta...@chromium.org, Nov 5

Status: Fixed (was: Assigned)
►

Sign in to add a comment