steamvr1.8.2.VulkanVblankThr.txt
General system logs from the time period of the crash. If I'm reading correctly it appears to originate from:
audit[4914]: ANOM_ABEND auid=1000 uid=1000 gid=100 ses=2 pid=4914 comm="VulkanVblankThr" exe="/home/vash/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor" sig=11 res=1
steam.desktop[1600]: crash_20190918132109_1.dmp[4975]: Uploading dump (out-of-process)
steam.desktop[1600]: /tmp/dumps/crash_20190918132109_1.dmp
crash_20190918132109_1.dmp[4975]: Uploading dump (out-of-process)
/tmp/dumps/crash_20190918132109_1.dmp
kernel: VulkanVblankThr[4933]: segfault at 0 ip 00007efbf90eecdd sp 00007efbf2f85cf0 error 4 in libnvidia-glcore.so.435.19.03[7efbf82b0000+12bc000]
kernel: Code: 89 c5 53 74 67 48 8b 05 f9 fe e6 00 4d 63 e8 4a 8d 3c ed 00 00 00 00 ff 10 85 ed 48 89 c3 7e 24 31 c9 31 d2 49 8b 04 d4 ff c1 <8b> 00 66 c7 44 d3 04 03 00 66 c7 44 d3 06 00 00 89 04 d3 48 ff c2
kernel: audit: type=1701 audit(1568805670.088:62): auid=1000 uid=1000 gid=100 ses=2 pid=4914 comm="VulkanVblankThr" exe="/home/vash/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor" sig=11 res=1
Nothing extracted yet.
Describe the bug
Crash in libnvidia-glcore immediately on launch in 1.8.2.
To Reproduce
Steps to reproduce the behavior:
Reproduction is simple, it crashes immediately on application launch, X11 freezes for ~15 seconds and then when it recovers SteamVR says it needs to close or restart. This is with the new SteamVR Beta 1.8.2 - there were a lot of changes to the compositor on Valve's end in the change notes and the older versions did not do this.
System Information (please complete the following information):
Additional context
As the issue seems to be in Nvidia code if I'm reading the logs correctly (which I'm attaching), I've also reported this to nvidia-bugs and will follow up here if they assign a bug on their end.
Also, this sounds very similar to #247 but for some reason they were able to generate the system report so I'm not confident that the details are identical. I also grepped their logs for the crash in 'VulkanVblankThr' (the first error line in my logs) and do not see it in their report so I'm not sure if the bugs are identical.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.