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

Issue 595162 link

Starred by 4 users
Status: WontFix
Owner:
sadrul@chromium.org
Closed: Jan 2017
Cc:
█ fsam...@chromium.org
sadrul@chromium.org
sky@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

0-copy client transport for mus

Project Member Reported by rjkroege@chromium.org, Mar 15 2016 
clients for mus-pixel (aka mus for ozone/gbm) need to have a ui::ClientNativePixmapFactory created for them for 0-copy pixel transfers.

More generally: we need a zero-copy image transfer solution for mus.

Comment 1 by fsam...@chromium.org, Mar 15 2016

Owner: penghuang@chromium.org
Passing to Peng.

Comment 2 by fsam...@chromium.org, Mar 15 2016

Owner: fsam...@chromium.org
Actually, I'll pick it up.

Comment 3 by rjkroege@chromium.org, Mar 21 2016

Components: MUS>Phase>1
Labels: pixelmus

Comment 4 by rjkroege@chromium.org, Oct 4 2016

Components: Internals>MUS
Labels: Proj-Mustash

Comment 5 by fsam...@chromium.org, Nov 27 2016

Cc: sadrul@chromium.org
This ought to be a non-issue now as we unify the gpu service in Mus+Ash with Chrome. WDYT, Sadrul?

Comment 6 by fsam...@chromium.org, Jan 23 2017

Owner: sadrul@chromium.org
Status: WontFix (was: Untriaged)
This is outdated, and I believe fixed. Marking as WontFix.

Comment 7 by lafo...@chromium.org, Feb 26 2018

Components: -Internals>MUS Internals>Services>WindowService

Comment 8 by lafo...@chromium.org, Feb 26 2018

Components: -MUS>Phase>1
►

Sign in to add a comment