Skip to content

Commit

Permalink
Doc: Update Chrome app recipe
Browse files Browse the repository at this point in the history
Referring to #229, passing --use-gl=egl to Chrome v112+ causes the GPU
process to crash, even when Chrome is run on a local display without
VirtualGL.  At the moment, there is no clean way to use Chrome/ANGLE
with VirtualGL, because when using ANGLE, Chrome obtains visuals using
raw GLX requests/replies (so there is nothing for VirtualGL to
interpose.)  Through some really messy modifications, VirtualGL can be
made to work with Chrome/ANGLE, but the performance is awful.  From
VirtualGL's point of view, these are pathological behaviors that the
Chrome developers need to resolve, much as the GTK developers resolved
them.  Until then, we cannot claim that Chrome works with VGL.
  • Loading branch information
dcommander committed Feb 20, 2024
1 parent d950b03 commit 476aacc
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 4 deletions.
6 changes: 5 additions & 1 deletion doc/apprecipes.txt
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@
layers of Python and shell scripts. The ''LD_PRELOAD'' variable does not \
get propagated down from the initial shell that invoked ''vglrun''. \
|
| Google Chrome/Chromium | v85 and later | Linux \
| Google Chrome/Chromium | v85 through v111 | Linux \
| ''vglrun google-chrome --disable-seccomp-filter-sandbox --use-gl=egl''{nl} \
or{nl} \
''vglrun chromium --disable-seccomp-filter-sandbox --use-gl=egl'' \
Expand All @@ -105,6 +105,10 @@
OpenGL rather than OpenGL ES, which works around an issue whereby, when \
using OpenGL ES, Chrome/Chromium assumes that every X visual has an EGL \
framebuffer configuration associated with it. \
{nl}{nl} \
Passing ''--use-gl=egl'' to Chrome v112 and later causes Chrome's GPU \
process to crash (regardless of whether VirtualGL is used), and as of \
this writing, there are no known workarounds. \
|
| Compiz | All | Linux \
| Set the ''VGL_WM'' environment variable to ''1'' prior to launching the \
Expand Down
6 changes: 3 additions & 3 deletions doc/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<meta name="language" content="en">
<meta name="date" content="2024-02-19T07:43:42">
<meta name="date" content="2024-02-20T15:49:46">
<meta name="generator" content="deplate.rb 0.8.5">
<title>User&rsquo;s Guide for VirtualGL 3.1.1</title>
<link rel="start" href="index.html" title="Frontpage">
Expand Down Expand Up @@ -2176,10 +2176,10 @@ <h1 id="hd0015"><a name="file015"></a>15&nbsp;Other Application Recipes</h1>
</tr>
<tr class="standard">
<td class="standard">Google Chrome/Chromium</td>
<td class="standard">v85 and later</td>
<td class="standard">v85 through v111</td>
<td class="standard">Linux</td>
<td class="standard"><code>vglrun&nbsp;google-chrome&nbsp;--disable-seccomp-filter-sandbox&nbsp;--use-gl=egl</code><br /> or<br /> <code>vglrun&nbsp;chromium&nbsp;--disable-seccomp-filter-sandbox&nbsp;--use-gl=egl</code></td>
<td class="standard">The <code>--disable-seccomp-filter-sandbox</code> option prevents Chrome/Chromium from complaining about the X11 function calls that the VirtualGL faker makes. The <code>--use-gl=egl</code> option forces Chrome/Chromium to use desktop OpenGL rather than OpenGL ES, which works around an issue whereby, when using OpenGL ES, Chrome/Chromium assumes that every X visual has an EGL framebuffer configuration associated with it.</td>
<td class="standard">The <code>--disable-seccomp-filter-sandbox</code> option prevents Chrome/Chromium from complaining about the X11 function calls that the VirtualGL faker makes. The <code>--use-gl=egl</code> option forces Chrome/Chromium to use desktop OpenGL rather than OpenGL ES, which works around an issue whereby, when using OpenGL ES, Chrome/Chromium assumes that every X visual has an EGL framebuffer configuration associated with it. <br /><br /> Passing <code>--use-gl=egl</code> to Chrome v112 and later causes Chrome&rsquo;s GPU process to crash (regardless of whether VirtualGL is used), and as of this writing, there are no known workarounds.</td>
</tr>
<tr class="standard">
<td class="standard">Compiz</td>
Expand Down

0 comments on commit 476aacc

Please sign in to comment.