I see a child process of vrwebhelper which is showing up with the executable name being /proc/self/exe. This is ‘really’ a Chromium bug which has been around for quite a while but which I've only today noticed in SteamVR.
There is a known interaction of this bug with some older versions of Unity, notably 5.3, in which the game checks for itself already running, finds a process using /proc/self/exe and follows the symlink – which is always going to point to the executable of the current process. Finding that, the game will exit immediately.
Expected behaviour: the game is launched normally. (Note that none of the affected Unity-based games have VR support.)
Workaround: don't have SteamVR running when trying to launch those games.
I see a child process of vrwebhelper which is showing up with the executable name being
/proc/self/exe. This is ‘really’ a Chromium bug which has been around for quite a while but which I've only today noticed in SteamVR.There is a known interaction of this bug with some older versions of Unity, notably 5.3, in which the game checks for itself already running, finds a process using /proc/self/exe and follows the symlink – which is always going to point to the executable of the current process. Finding that, the game will exit immediately.
Expected behaviour: the game is launched normally. (Note that none of the affected Unity-based games have VR support.)
Workaround: don't have SteamVR running when trying to launch those games.
(SteamVR 1.12.3.)