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

Issue 735057 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
danakj@chromium.org
penghuang@chromium.org
█ fsam...@chromium.org
sadrul@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 732805



Sign in to add a comment

Mus doesn't configure overlay support

Project Member Reported by rjkroege@chromium.org, Jun 20 2017 
viz::CompositorOverlayCandidateValidatorOzone doesn't get built by the mus Gpu host. In particular, it's only created here: https://cs.chromium.org/chromium/src/content/browser/compositor/gpu_process_transport_factory.cc?rcl=aa22fa5e688e165d704990b2e18b9c1f73c2ab4c&l=281

Note that this object is a Gpu service "client" component and needs to built in the same process as the display compositor.

penghuang@: fyi this will almost certainly cause a performance regression in EXO compared when running with --mus vs standard CrOS when the device supports overlays.
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 20 2018

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

Comment 2 by rjkroege@chromium.org, Jun 21 2018

Status: WontFix (was: Untriaged)
mus overlay support is a non-goal. (As opposed to Viz overlay support which is being actively worked on.) Closing as obsolete.
►

Sign in to add a comment