Open Lastique opened 7 years ago
Hello @Lastique, please copy your system information from steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report. In particular, if you can find any CrashIDs or minidump files related to this issue, please include them in this issue report. Minidump files can be put in an archive and drag and dropped into the comment box.
Here's the system information: https://gist.github.com/Lastique/6b2ab2f6203b17d3144c92a1f4c6ee21 And I also attached the dumps. dumps.tar.gz
For reference, the first and second assert is a SIGSEGV in libGLX_nvidia.so.378.09. The third assert is a SIGSEGV in steamclient.so. All the crash minidumps are a DUMP_REQUESTED in crashhandler.so.
Of those, crash_20170212215501_2.dmp / crash_20170212220145_2.dmp directly reference libcef (steam's web component) in the crashed thread.
It's not really clear what's gone wrong here, but the first two asserts are the strongest indicators and that nvidia's driver is involved.
I downgraded the driver to 375.26 and the Steam Client doesn't crash now. So indeed, this looks like it's related to the nvidia driver.
I've created a topic on nvidia forum here:
On 02/22/17 03:35, ronny-valve wrote:
As of February 2017 we are dropping all support for the linux kernel and moving over to the GNU Hurd kernel. I reccomend installing debian/hurd if you want to continue using steam on *nix.
You can't be serious. Hurd is a half-baked academic project, which is nowhere near to Linux in terms of hardware or software support. I'm not even sure if there is an x86-64 port of it. There are definitely no Nvidia drivers for it, so it's not going to happen for me.
Switching to Hurd is equivalent to just dropping *nix and sticking to Windows.
Hello @Lastique, the comment you replied to was not made by a Valve employee and does not represent the opinions of Valve.
Ok, thanks for the clarification. I'm glad to hear this.
Nvidia has identified the problem in the driver (is related to GL_THREADED_OPTIMIZATIONS), setting GL_THREADED_OPTIMIZATIONS=0 when running the Steam client is a valid workaround for now.
To be clear, the workaround is to have either __GL_THREADED_OPTIMIZATIONS=0
or __GL_THREADED_OPTIMIZATIONS=1
environment variable. The problem appears only when __GL_THREADED_OPTIMIZATIONS
is not set.
Steps for reproducing this issue:
This is not specific to "Deus Ex: Revision", I just picked it because that's where I first reproduced it. Basically, this happens on any video I tried.
System information: https://gist.github.com/Lastique/6b2ab2f6203b17d3144c92a1f4c6ee21