Not seeing anything in the log indicating a crash (what are the exact symptoms here?), nor do I see why that commit would be an issue in one particular game while working fine with literally everything else.
Edit: nvm, there's this:
*** stack smashing detected ***: terminated
unfortunately this is less than helpful.
Guess I can just revert the commit, but doing so does have downsides and I'd rather understand what the problem is. Really need to find a different game to debug that with though.
On second thought, no, I think I understand what's going on. The game probably unloads d3d11.dll while the device is still alive, so the thread wakes up while its address space is already unmapped. Common, recurring issue, I really need to remind myself that DXVK can never have threads that periodically wake up.
d3d11.dllx1 2026-06
The "Diablo Immortal" game crashes during the file updating/checking stage before the main game starts.
The issue started with commit 9fbbc689e1741bf378ebc1be7b512a13b0ff8c24, and reverting it allows the game to start.
System information
DI-dxvk-3.0-bug.log.txt