Hello @Hanoj05, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-6376385453.
proton experimentalx1 2026-10PROTON_LOG=1x1 2026-10
Compatibility Report
Summary
Overwatch (App ID 2357570) crashes at random during play with a native SIGSEGV
in the game's wine64-preloader process. The game freezes (while a core dump is
written) and then dies. There is no Windows-side exception and no Wine error.
It happens every few sessions, with no pattern in what I'm doing at the time.
System Information
layers are installed on the system but not active); Reflex off in-game
I confirm:
Symptoms
Overwatch (App ID 2357570) crashes at random during play with a native SIGSEGV
in the game's wine64-preloader process. The game freezes (while systemd writes a
core dump) and then dies. There is no Windows-side exception and no Wine error
in the log. It happens every few sessions, after anywhere from minutes to about
an hour, with no pattern in what I'm doing at the time.
What I found
Two core dumps (Oct 18 and Oct 23) crash at the same place, inside
Proton Experimental's lib/wine/x86_64-unix/ntdll.so:
save_context+0x... (file offset 0x49d9a)
49d95: call NtCurrentTeb
49d9a: mov 0x2f0(%rax),%rax <-- faults
So NtCurrentTeb() returns an invalid pointer inside a signal handler
(save_context), and the next read from it faults. The gdb dump is attached.
The dump is truncated, so I couldn't capture rax or the stack, and I don't
know why the TEB pointer is invalid.
History
coredumpctllists 11 wine64-preloader SIGSEGVs between 2026-09-20 and2026-10-23. I checked the command line for the first 9 and all are
Overwatch.exe. The last two are the dumps above.
so it is not specific to one Proton build.
vanishes. It shows Blizzard's usual int3 / assertion exception every 10 s,
which is handled normally.
Logs
Reproduction
Play Overwatch normally. It happens after anywhere from minutes to about an
hour. I can't reproduce it on demand.
Logs.zip
Logs
kernel 7.2.9-ogc3.1). The game ran ~3 hours with the usual Blizzard int3 /
assertion exception every 10 s, then the process vanished with no Wine
exception, Vulkan error or other message in the log.
Oct 23 core dump (same crash address as the Oct 18 dump, low 12 bits).
Disclaimer: Yes i used AI for this, because i am definitely not smart enough to figure out all that myself! :)