Mad Max (234140)

Compatibility Report

• Name of the game with compatibility issues: Mad Max
• Steam AppID of the game: 234140

System Information

• GPU: GTX 1080
• Driver/LLVM version: nvidia 450.66
• Kernel version: 5.4
• Link to full system information report as Gist: https://gist.github.com/AlexP11223/7506e04f1619d361761b1e0c4441e96b
• Proton version: 5.0.9, 5.0.10 RC

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms && Reproduction

Playing Mad Max with Proton as suggested in ProtonDB (the native version from Feral has worse performance, no 144 Hz, etc.). Everything is fine, 140+ fps.
Except these weird crashes.

It crashes if I start the game and drive from a stronghold to any "distant" point. Always in the same place.
For example:

If I go somewhere near the stronghold first, complete some activities nearby, then later everything is fine and I can drive anywhere. So it crashes only if I go too far away too quickly after loading the game :D

In Proton log I found only this at the end:

...
679.609:023c:0240:trace:seh:execute_cfa_instructions 7f85d89ea264: DW_CFA_def_cfa %rsp, 8
679.609:023c:0240:trace:seh:execute_cfa_instructions 7f85d89ea264: DW_CFA_advance_loc 1
679.609:023c:0240:trace:seh:execute_cfa_instructions 7f85d89ea265: DW_CFA_restore_state
679.609:023c:0240:err:seh:setup_exception stack overflow 1632 bytes in thread 0240 eip 00007f85db837228 esp 0000000000120fb0 stack 0x120000-0x121000-0x220000
680.708:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winehid.sys" : builtin
680.708:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\hidclass.sys" : builtin
680.710:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winebus.sys" : builtin
pid 9175 != 9174, skipping destruction (fork without exec?)

Full log: https://drive.google.com/uc?export=download&id=1IlIokJcYy7oN6YO580kXh8uOqNEW3CN3

The native version doesn't have this issue.

No source file or test is named. Start by reproducing the crash with Mad Max under Proton 5.0.9 or 5.0.10 RC, then inspect the linked Proton log and system report alongside the reproduction steps. Done means narrowing the crash to a confirmed Proton component and documenting or validating a fix.