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

Issue 732594 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 732805
Owner: ----
Closed: Aug 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on: View detail
issue 655231
issue 670710

Blocking:
issue 773453



Sign in to add a comment

Make out-of-process display compositor work with mus/window server

Project Member Reported by danakj@chromium.org, Jun 12 2017

Issue description

This is the delta once we have a display compositor in the gpu process, to make that work correctly with a WindowServer once that responsibility is split out of the browser process.
 

Comment 1 by danakj@chromium.org, Jun 12 2017

Blocking: 601863

Comment 2 by danakj@chromium.org, Jun 12 2017

Blockedon: 670710

Comment 3 by danakj@chromium.org, Jun 12 2017

Blockedon: 655231

Comment 4 by fsamuel@google.com, Oct 10 2017

Blocking: 773453
Components: MUS
Labels: mus
Components: -MUS Internals>Compositing Internals>Services>Viz
Labels: -mus Proj-Ozone Proj-Mustash
CrOS I presume?

Comment 7 by danakj@chromium.org, Jan 29 2018

Blocking: -601863
Yeh.. or maybe just not blocking task, cuz we can do chromeos without this. https://bugs.chromium.org/p/chromium/issues/detail?id=732805 is for chromeos so lets say the latter.
Labels: -Proj-Mustash Proj-Mash-MultiProcess
Bug scrub: Is this needed for mustash/out-of-process ash?

Mergedinto: 732805
Status: Duplicate (was: Available)
It's required for when you actually run ash and browser in separate processes. The implementation is covered by other bugs.

Sign in to add a comment