That error is benign and is fixed on master. It's related to waitable swapchain fence. We try to ReleaseSemaphore(), but the count is already saturated.
Ok, so it's most likely not the source of the crash. Do you have a guess based on the log?
Nothing obvious. The "Not supported for queue type 2" thing is also fixed long ago.
Latest proton-experimental (using vkd3d 2.5.0) shows the same crash behavior, but different messages in the log.
For example fence_signal_event: Failed to release semaphore. Application likely forgot to wait for presentation event. is new.
The eventual crashes were caused by Mangohud. After confirming the issue again I've disabled Mangohud and played for 2x 1 hour without a single crash. (Tested with Mangohud 0.6.5)
proton experimentalx2 2021-11proton 6.3-7x1 2021-11PROTON_LOG=1`x1 2021-11
Description
Started playing Cyberpunk 2077 a few days ago. From the start I saw crashes after ~30 minutes of gameplay. Enabling
PROTON_LOG=1shows a huge amount ofd3d12_fence_signal_external_events_locked: Failed to signal event, hr #80004005.errors and differentwarn:d3d12_command_list_*warnings.I'm able to reproduce the issue on Proton 6.3-7 (vkd3d 2.4.0) and Proton Experimental (vkd3d 2.5.0).
Looking further into it
The fence errors are reported while UI is displayed. The eventual crash always happens on opening an UI (opening main menu using Escape or I to open the Inventory UI). Staying in the main menu also leads to a crash after ~5 minutes (seen once so far).
Specs
Full Log
steam-1091500.zip