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

Issue 703950 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Land Wayland alternative allocation API upstream.

Project Member Reported by hannia@chromium.org, Mar 22 2017

Issue description

Land Wayland alternative allocation API upstream for Android Studio
 

Comment 1 by za...@chromium.org, Mar 23 2017

Cc: hoegsberg@chromium.org reve...@chromium.org
We still need to figure out what that might look like and how likely it is that upstream will want it. We also have the possible alternative of using the dma buf extensions.
What's the context here?

Comment 3 by za...@chromium.org, Mar 23 2017

This is the running Android Studio in a virtual machine with virtio-wayland project. The problem is that wayland client libraries (gtk, qt, xwayland) fall back to using buffers backed by shared memory allocated client-side. However, virtio-wayland requires server-side allocations to properly share memory with the host compositor. It's been proposed that wayland should have a built in way to have clients request a buffer be made server side, which would solve this problem.
Labels: OS-Chrome

Comment 5 by dgreid@chromium.org, Nov 18 2017

Status: WontFix (was: Untriaged)
Components: OS>Systems>Containers

Comment 7 by vapier@chromium.org, May 17 2018

Labels: -Restrict-View-Google

Sign in to add a comment