#76 "Could not clone X display connection" with Chrome and TurboVNC

[Oleg Pereverzev]

This issue only occurs when using VirtualGL
This issue does not occur with simple applications and even SuperTuxKart, it is google-chrome specific
Always reproducable,
VirtualGL 2.4 (tried both precompiled deb and compiling from source)
TurboVNC 1.2.90
Google Chrome unstable 43.0.2357.18 and 44.0.2391.0, Google Chrome stable 42.0.2311.152
Nvidia Driver 340.76 (also tested on 346.72)
X.Org X Server 1.15.1

Hardware: 2xXeon, 128Gb RAM, GeForce GTX 750 Ti + disabled Matrox MGA G200e

Log file is http://fpaste.org/221788/, problem is that Chrome starts after all, but it is not accelerated.

[VGL] [VGL] ERROR: in VirtualWin--
[VGL] 78: Could not clone X display connection

I saw in sourcecode you are checking and throwing that error, that means it is somewhat predicted, but as it is specific to Chrome and has no documentation on fixing i fill it as a bug.

[Oleg Pereverzev]

Also the reproduction case: I just start google-chrome in TurboVNC via vglrun, on :0 there is an up and working X with Nvidia video configured.
Why is it platform-specific? Because the same software works like a charm on PC with ATI video

[DRC]

The only way (that I know of) to get Chrome to work in VGL is to pass --disable-gpu-sandbox to Chrome. Otherwise, it tries to create a separate process for 3D rendering (WebGL), and that trips up VirtualGL's interposer.

But you're saying that it works with VirtualGL if using an ATI GPU on display :0 but not nVidia? That seems odd. Anyway, try --disable-gpu-sandbox and see if that fixes it.

[Oleg Pereverzev]

Well, that did the trick. Yeah, maybe it runs in single process by default when detects ATI card, who knows what is in binary there.
Mention please somewhere this issue with google-chrome and overall child processes so there will be no such stupid bugeports as this one. Thanks.

[DRC]

It's mentioned in the "Application Recipes" section of the VirtualGL 2.4 (and later) User's Guide