New issue
Advanced search Search tips

Issue 848924 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 264818
Owner:
Closed: Sep 4
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 848856



Sign in to add a comment

Enable GPU Sandbox in CrOS/Chrome on Nouveau

Project Member Reported by rjkroege@chromium.org, Jun 1 2018

Issue description

When attempting to run CrOS/Chrome on Linux/Nvidia/Nouveau like this:

sudo chvt 8; EGL_PLATFORM=surfaceless $CHROMIUM_SRC/out/Nouveau/chrome --ozone-platform=gbm --force-system-compositor-mode --login-profile=user --user-data-dir=$HOME/.config/google-chrome-gbm --ui-prioritize-in-gpu-process --use-gl=egl --gpu-sandbox-failures-fatal=yes --enable-wayland-server --login-manager --ash-constrain-pointer-to-root --default-tile-width=512 --default-tile-height=512 --system-developer-mode --crosh-command=/bin/bash

Chrome fails when attempting to initialize the GPU process because it sandbox setup and thread creation happen in the wrong order. I presume that the Nouveau driver creates additional threads at an inopportune time.
 
Blocking: 848856
Components: Internals>GPU
Owner: rjkroege@chromium.org
Status: Assigned (was: Untriaged)
rjkroege: can you assign this to somebody?
Mergedinto: 264818
Owner: moh...@chromium.org
Status: Duplicate (was: Assigned)
Re #4: I think this bug is effectively a duplicate of the one that you've listed.


Sign in to add a comment