search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.31k stars 1.06k forks source link

God of War (1593500) #5511

Open HolySoap opened 2 years ago

HolySoap commented 2 years ago

Compatibility Report

System Information

I confirm:

steam-1593500.zip Note: The log file is from a different run where the slide-show happened after ~2,5h and the RAM climbed to a high of 28,7 GiB.

Symptoms

Memory Leak System in idle before the I start the game. idle_2022-01-21_12:08:04 System after I pressed "continue" and loaded into the world. after_load_2022-01-21_12:09:38 System when the slide-show started, about 1,5h in. Note: It was right after a cutscene and in that cutscene the RAM climbed above 24GiB slideshow_2022-01-21_13:29:50

When the RAM consumption reaches an all time high (not necessarily all the RAM available) it goes down a little and the slide-show begins.

Reproduction

Playing for around two hours, happens every single time. Depending on how many cutscenes someone encounters in a session it can happen sooner or later.

Leopard1907 commented 2 years ago

Fwiw, this seems to be a game issue that affects multiple people on Windows as well which has a stickied thread from devs in order to gather info.

https://steamcommunity.com/app/1593500/discussions/1/3202622816426786475/

HolySoap commented 2 years ago

I see, but this bug should still be observed even if they patch it or maybe its fixable in Proton.

ambasta commented 2 years ago

Another issue on Vega cards as well. The game seems to cause VM_PROTECTION_FAULTS on amdgpu

Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32777, for process GoW.exe pid 2614 thread dxvk-submit pid 2657)
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00008001b0080000 from IH client 0x1b (UTCL2)
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00401030
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
Jan 22 18:00:51 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
Jan 22 18:01:01 antirez kernel: [drm:0xffffffff818fc870] *ERROR* Waiting for fences timed out!
Jan 22 18:01:01 antirez kernel: [drm:0xffffffff81852c32] *ERROR* ring gfx timeout, but soft recovered
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32777, for process GoW.exe pid 2614 thread dxvk-submit pid 2657)
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00008001b0080000 from IH client 0x1b (UTCL2)
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00401030
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
Jan 22 18:01:07 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
Jan 22 18:01:17 antirez kernel: [drm:0xffffffff818fc870] *ERROR* Waiting for fences timed out!
Jan 22 18:01:17 antirez kernel: [drm:0xffffffff81852c32] *ERROR* ring gfx timeout, but soft recovered
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32777, for process GoW.exe pid 2614 thread dxvk-submit pid 2657)
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00008001b0080000 from IH client 0x1b (UTCL2)
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00401030
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
Jan 22 18:01:31 antirez kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
Jan 22 18:01:41 antirez kernel: [drm:0xffffffff818fc870] *ERROR* Waiting for fences timed out!

This leads to the GPU being unresponsive until soft recovery and causes the game to freeze every 10-30 seconds.

kisak-valve commented 2 years ago

Hello @ambasta, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

ambasta commented 2 years ago

Here's a gist against the system information as requested @kisak-valve

gort818 commented 2 years ago

They claim to have fixed the memory leak issue https://steamcommunity.com/games/1593500/announcements/detail/3128314055444329136

HolySoap commented 2 years ago

They claim to have fixed the memory leak issue steamcommunity.com/games/1593500/announcements/detail/3128314055444329136

I have seen that yesterday, but they released it way too late for me to try it out. I will report back in a few hours after some testing.

HolySoap commented 2 years ago

After three hours of playing I think its safe to say that the Memory Leak is fixed and can be marked as solved and maybe closed.

After loading into the save the RAM usage climbed 2,5 GiB more over a period of ~30min and was consistently stuck (in my case) at 14,4 and 14,9 GiB depending on the world.

leotada commented 2 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/5511#issuecomment-1019244651

I'm having this issue too with my AMD Vega 56 card.

hakzsam commented 2 years ago

Are you still able to reproduce issues with RADV? It looks like Vega might still be affected but what about other GPUs?

coreybruce commented 1 year ago

Can the crashing if you alt tab out of the game be fixed also? kinda annoying especially if you just need to fix or change something and come back to the game.

coreybruce commented 1 year ago

Here is my latest log from my Gaming PC where instead of crashing it would just get stuck on a black screen when I alt tab off the game which it shouldn't do

https://gist.github.com/coreybruce/d69e9b92cdf05696378110dd06e838dc

Log was either to big in file size or to long to upload it all but here is a piece of it

LiamDawe commented 1 year ago

Log file: steam-1593500.zip

The memory leak still clearly happens on Steam Deck, as it will easily hard crash the entire Steam Deck after a while. Multiple reporte of this on ProtonDB too. Should not be Verified.

It hits about 14.2GB RAM then just dies.

01269E84-912C-4FE2-8110-C5285B35258E

This is with the default Proton 7.0-5.

nebadon2025 commented 1 year ago

I was able to replicate the exact situation as @LiamDawe above me here got to 14.2gb memory after less than 1 hour of play and steam deck froze hard! Seems like perhaps a memory leak leading to total system failure, my deck did not reboot on its own, it remained frozen in the state showing 6fps but none of the keys were functional after 5 minutes I hard powered off myself because the unit remained hot even though it was totally frozen. As a side note, this testing was done using Proton-Experimental (Bleeding Edge) as of the date of this posting fully updated and also on the Beta Steam Deck OS. GOW_CRASH

also took series of screenshots showing the memory climbing on mangohud. https://steamcommunity.com/sharedfiles/filedetails/?id=2922106366 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106605 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106447 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106700 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106664 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106744 https://steamcommunity.com/sharedfiles/filedetails/?id=2922106780

LiamDawe commented 1 year ago

Log file: steam-1593500.zip Confirming also the hard crash and deck reboot issue also happens on bleeding edge experimental.

rjousse18 commented 1 year ago

Same here, I had to hard reboot my steam deck. The game crashed 2 or 3 times since I start the game.

zaggynl commented 1 year ago

After applying the changes from https://github.com/CryoByte33/steam-deck-utilities, GoW no longer crashes every 45-60 minutes on Steam deck.

Strawbecci commented 1 year ago

God of War doesnt start at my PC, it crashes directly after the Sony Screen, my Hardware is a Intel Core i5 10400F with a RX 5700xt. I have tried different distros and Proton versions. All have the same issue.

crashlog.tar.gz

zaggynl commented 1 year ago

For reference a quick test on my PC: first start attempt nothing appeared to happen, had to wait until fossilize_replay process finished, after that the game started. After the Sony logo a Playstation Studio(?) screen appears.

sysinfo: steam_system_information.txt

proton log: steam-1593500.zip

coreybruce commented 1 year ago

God of War doesnt start at my PC, it crashes directly after the Sony Screen, my Hardware is a Intel Core i5 10400F with a RX 5700xt. I have tried different distros and Proton versions. All have the same issue.

crashlog.tar.gz

Try clearing the compatdata folder for the game and make sure to use the latest proton stable 8.0-2

kisak-valve commented 1 year ago

Hello @Strawbecci, looking at your Proton log, the snafu you've encountered is audio related:

err:pulse:pulse_spec_from_waveformat Invalid channel mask: 0/12 and 0(0)
[...]
err:pulse:pulse_spec_from_waveformat Invalid format! Channel spec valid: 0, format: 5
[...]
err:dsound:DSOUND_ReopenDevice Initialize failed: 88890008
[...]
Backtrace:
=>0 0x000000031ae0c134 CreateAudioReverb+0x14884() in xaudio2_9 (0x0000000000000000)
  1 0x000000007b62d759 ActivateActCtx+0x218a9() in kernel32 (0x0000000000000000)
  2 0x000000017005f707 A_SHAFinal+0x3caa7() in ntdll (0x0000000000000000)
0x000000031ae0c134 xaudio2_9+0x1c134: movq  (%rcx),%rax
Strawbecci commented 1 year ago

Hi @kisak-valve

Set the Soundserver to Alsa via protontricks fix my issue, thank you. :)

kisak-valve commented 1 year ago

God of War crashes when Alt Tabbing

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7037. @coreybruce posted on 2023-08-22T13:51:11:

Compatibility Report

System Information

I confirm:

Proton Log: https://raw.githubusercontent.com/coreybruce/Bulk-logs/main/steam-1593500.log

Symptoms

Game will crash if you alt tab from the game and it will always crash

Screenshot from 2023-08-22 23-20-24

Reproduction

Alt tab off game and go back

Brenonxcoder commented 10 months ago

I didn't have such problems, maybe because I bought it in a reliable store. I recommend this store because that's where I bought it.

kisak-valve commented 6 months ago

Atmospherics stuck on low in God of War 2018

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7635. @babiescanfly posted on 2024-04-04T23:25:44:

Compatibility Report

System Information

I confirm:

Symptoms

Even if atmospherics in the graphics menu are set to anything other than low (including presets) the game will still use the low version. If a custom setting is used the game will always reset atmospherics to low.

Reproduction

Always occours. Can't find an instance where it doesn't.