[L4D2] Segfault in libdxvk_d3d9.so when Vulkan is enabled.

[Oliver-1xok]

I play the latest L4D2 version on my DELL Linux-Laptop with an i7-7820HQ CPU and get a segfault. My CPU uses the integrated HD Graphics 630 (with Mesa 20.2.6). Operating System: Xubuntu 20.04.2 LTS (64 bit). Detailed system information below.

Steps to reproduce:

1. Set the new -vulkan option as launch parameter.
2. Start the game.
3. Play campaign single player.
4. During the loading screen the segault occurs.

Excerpt from my ring buffer:

MatQueue0[7613]: segfault at 389 ip 00000000e772dc13 sp 000000008c3a83b0 error 4 in libdxvk_d3d9.so[e7653000+325000] [ 3671.116208] Code: 86 34 0b 00 00 39 c7 0f 84 ca 01 00 00 85 c0 0f 84 02 02 00 00 0f b6 9e 38 e3 02 00 8d 50 10 85 ff 0f 84 c0 01 00 00 8d 4f 10 <80> bf a8 02 00 00 00 89 4d dc 0f 84 3d 01 00 00 c6 86 38 e3 02 00

Dump attached: assert_20210621215501_1.dmp.gz

This does not happen (unsurprisingly) with the OpenGL version of the game. It also doesn't happen on a system with a dedicated Nvidia graphics card.

System Information from my DELL system (where the segfaut occurs): https://gist.github.com/Oliver-1xok/55e3c42f42aac88a19d57244a155631a#file-steam-system-information

[kelnos]

I just started seeing the same thing, running Debian testing (bookworm). I just got a new Framework Laptop (Intel 12th-gen with Intel Xe graphics; Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)). Removing -vulkan from the command line options (reverting to OpenGL) allows me to play without a crash. This used to work fine on my Dell XPS 13 (which was also running Debian testing). dmesg shows:

MatQueue0[133890]: segfault at 24cdc313 ip 00000000d86dc033 sp 0000000067ec2860 error 4 in libdxvk_d3d9.so[d8600000+337000]
Code: 86 88 0d 00 00 39 c7 0f 84 da 01 00 00 85 c0 0f 84 12 02 00 00 0f b6 9e b4 02 00 00 8d 50 10 85 ff 0f 84 d0 01 00 00 8d 4f 10 <80> bf a8 02 00 00 00 89 4d dc 0f 84 4d 01 00 00 c6 86 b4 02 00 00

Dump: crash_20220813221859_14.dmp.gz