PSA: Chrome GPU sandbox failures are now fatal

375 views
Skip to first unread message

Jorge Lucangeli Obes

unread,
Mar 24, 2014, 6:33:05 PM3/24/14
to chromium-dev
Hi all,

TL;DR: Chrome will now LOG(FATAL) if it cannot enable the GPU sandbox. If you're working on new board bring-up, you can pass --gpu-sandbox-failures-fatal=no until the sandbox supports this new driver/GPU.

A CL has just landed making GPU sandbox failures on Chrome OS fatal. Previously, we were allowing the GPU sandbox to fail silently because we had some bugs around thread detection. These bugs have been fixed so we want to make sure that we detect regressions where the GPU sandbox fails to initialize, and we don't expose users to these regressions.

The CL went through the CQ so I don't expect major issues. For new board bring-up, the --gpu-sandbox-failures-fatal=no command-line flag can be used until we make the sandbox work with that driver/GPU.

Feel free to contact me if you see Chrome not starting and LOG(FATAL) messages about the GPU sandbox in the logs.

Cheers,
Jorge

Jorge Lucangeli Obes

unread,
Mar 24, 2014, 6:35:02 PM3/24/14
to chromium-dev
This was actually for chromium-os-dev@. There's no change on other platforms.
Reply all
Reply to author
Forward
0 new messages