ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.21k stars 174 forks source link

fossilize replay never ends. #8593

Open Redbatman89 opened 2 years ago

Redbatman89 commented 2 years ago

So upon restarting steam if the process Allow Background Shades is enabled it will be stuck at zero and fossilize replay will be running at multiple instances and refuses to stop, cant even kill process. Have to hard shutdown to stop it.

kisak-valve commented 2 years ago

Hello @Redbatman89, please reproduce the issue, then wait a few minutes and attach ~/.local/share/Steam/logs/shader_log.txt as a file to this issue report. Hopefully there's a hint in there for a Steam dev to ponder. It also would be good to know if fossilize_replay was started before or after the Steam client restart.

Redbatman89 commented 2 years ago

Hello @Redbatman89, please reproduce the issue, then wait a few minutes and attach ~/.local/share/Steam/logs/shader_log.txt as a file to this issue report. Hopefully there's a hint in there for a Steam dev to ponder. It also would be good to know if fossilize_replay was started before or after the Steam client restart.

What happens is that even If I kill steam or shut it down, fossilize replay would still be running

kisak-valve commented 2 years ago

That sounds like https://github.com/ValveSoftware/steam-for-linux/issues/8113, which is not endless, but with the Steam client not waiting on Fossilize to finish its current job. If that's the case, then this is an improvement over the previous behavior as Steam can finish restarting and it should start to make visible progress once the previous background job finishes naturally.

Redbatman89 commented 2 years ago

That sounds like #8113, which is not endless, but with the Steam client not waiting on Fossilize to finish its current job. If that's the case, then this is an improvement over the previous behavior as Steam can finish restarting and it should start to make visible progress once the previous background job finishes naturally.

When I mean hard shut down, I actually had to as if I had just did normal shutdown via power off SystemMD would be say "Waiting for fossilize replay to end" And it would just hang there.

Hubro commented 12 months ago

Found this issue through Google - I thought my fossilize_replay processes had bugged since they've been running 8 threads (og my 32 thread CPU) on 100% for over an hour now. Checking the shader log as suggested by @kisak-valve, I see that it's indeed progressing, just extremely slowly.

In the last 15 minutes, it has progressed from 61% to 64% :thinking:

pslq commented 11 months ago

In my case was stuck for 6 hours until I eventually hit "skip"