Hello @mibli, it looks like you attached a general stdout/stderr log instead of a Proton log. Please add PROTON_LOG=1 %command% to the game's launch options, reproduce the game hang you're seeing, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Hello @mibli, it looks like you attached a general stdout/stderr log instead of a Proton log. Please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the game hang you're seeing, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Thanks for letting me know. I did what You suggested. Here's the link to the added tar.gz
Looks like an access violation (c0000005) happened around 8592.232, which lead to err:fsync:get_shm Failed to map page 63317 (offset 0xf755000). and the err:virtual:alloc_area_in_reserved_or_between_callback Could not map in reserved area. part\Endzone.exe: ../../../../proton/wine/dlls/ntdll/unix/virtual.c:1217: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed. asserts are fallout after the was game already in a bad state.
You might get lucky running with PROTON_NO_FSYNC=1 %command% or PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% in the game's launch options, but that might only delay the issue or degrade performance.
You might get lucky running with
PROTON_NO_FSYNC=1 %command%orPROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%in the game's launch options, but that might only delay the issue or degrade performance.
Yep I was just able to play almost 3 hours without crashing with FSYNC disabled, and no meaningful performance drop for me. This is good enough, even if the issue is delayed.
I realize that the issue is old and may be no longer relevant, but I confirm that PROTON_NO_FSYNC=1 is still required to avoid crashes in endzone as of March 2022 (1 year later) with latest Proton Experimental, disabling ESYNC is not required.
Endzone - A World Apart ( 933820 )
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7983.
@GhChancellor posted on 2024-08-12T08:24:25:
The game doesn't start at all. It only "runs" for a few seconds before stopping.
I've tried GE-Proton 9.11, Proton Experimental, Proton 9.0-2, Proton 8.0-5, Proton 7.0-6, Proton 6.3-8, Proton 5.13-6, Proton 5.0-10.
I've also tested various launch options like:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
The game doesn't start at all. It only "runs" for a few seconds (the initial loading screen) before stopping.
proton experimentalx2 2024-08proton 5.0-10x1 2024-08proton 5.13-6x1 2024-08proton 6.3-8x1 2024-08proton 7.0-6x1 2024-08proton 8.0-5x1 2024-08proton 9.0-2x1 2024-08proton 9.11x1 2024-08PROTON_NO_ESYNC=1x3 2024-08PROTON_NO_FSYNC=1x3 2024-08PROTON_NO_FSYNC=1`x1 2022-03PROTON_LOG=1x2 2021-03PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%x1 2024-08PROTON_NO_FSYNC=1 %command%x2 2021-03PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%x2 2021-03
Compatibility Report
Name of the game with compatibility issues: Endzone: A World Apart
Steam AppID of the game: 933820
System Information
OS: Manjaro Linux
KERNEL: 5.4.105-1-MANJARO
CPU: AMD Ryzen 5 3600 6-Core
GPU: AMD AMD Radeon RX 5600 XT (NAVI10, DRM 3.35.0, 5.4.105-1-MANJARO, LLVM 11.1.0)
GPU DRIVER: 4.6 Mesa 20.3.4
RAM: 16 GB
Proton version: 5.13-6
I confirm:
steam-stdout.log
steam-933820.log.tar.gz
Symptoms
Game hangs up suddently and has to be stopped with steam's "STOP" button.
Reproduction steps