Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam seems to never finish shader pre-compiling in the background for A Hat in Time #224

Open
MateusRodCosta opened this issue Jun 22, 2023 · 8 comments

Comments

@MateusRodCosta
Copy link

MateusRodCosta commented Jun 22, 2023

Your system information

  • Steam client version (build number or date): Wed, Jun 21 6:18 PM UTC -03:00

  • Distribution (e.g. Ubuntu): Fedora Silverblue 38, running as a Flatpak

  • Opted into Steam client beta?: [Yes/No] Yes

  • Have you checked for system updates?: [Yes/No] Yes

  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] steam-logs.tar.gz

  • GPU: NVIDIA GeForce GTX 1660 Ti / Intel® UHD Graphics 630

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

I have the option "Allow background processing of Vulkan shaders enabled" and I have several games installed, including A Hat in Time".
There's seems to be no indicator right now on the Steam UI that it's doing shader processing (there was one before the rollout of the new UI, I didn't find it after the redesign), but I can know due to the fan of the laptop speeding up.

The problem seems to be that the A Hat in Time shader compiling never finishes, I know it's stuck in the A Hat In time compiling because by checking htop fossilize_replay is working on the Steam app with the id of 253230 (which is A Hat in Time), also if I manually try to load A Hat in Time, but the compilation at that point also takes a long time, so I given up.
Letting the computer go 3 hours straight doing not more then shader compiling seems to not help, as apaprently it still doesn't do much progress.

Also, it seems sometimes the fossilize_replay can be crash, such as this:

jun 21 22:14:34 centauro kernel: traps: fossilize_repla[17788] general protection fault ip:7fd6aca926a4 sp:7ffd57e75568 error:0 in libc.so.6[7fd6aca28000+180000]
jun 21 22:14:36 centauro systemd-coredump[18576]: [🡕] Process 17788 (fossilize_repla) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1984:
                                                  #0  0x00007fd6aca926a4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x926a4)
                                                  ELF object binary architecture: AMD x86-64

Steps for reproducing this issue:

  1. Enable "Allow background processing of Vulkan shaders" feature
  2. Install A Hat In Time
  3. Check if it properly compiles A Hat In Time shaders
@kisak-valve kisak-valve transferred this issue from ValveSoftware/steam-for-linux Jun 22, 2023
@kisak-valve
Copy link
Member

kisak-valve commented Jun 22, 2023

Hello @MateusRodCosta, since this issue report focuses on the behavior of fossilize, I've transferred it to the fossilize issue tracker.

Can you check if (Steam install folder)/logs/shader_log.txt has any hints related to 253230 (A Hat in Time's appid)? already shared

@kisak-valve
Copy link
Member

Skimming over shader_log.txt and shader_log.previous.txt, I'm not seeing anything critically unusual.

@MateusRodCosta
Copy link
Author

Skimming over shader_log.txt and shader_log.previous.txt, I'm not seeing anything critically unusual.

Maybe it's hitting something in the Flatpak sandbox?

@MateusRodCosta
Copy link
Author

I have also these two from yesterday in ABRT in case it's any useful:

Captura de tela de 2023-06-22 12-32-37

Captura de tela de 2023-06-22 12-32-54

@kakra
Copy link
Contributor

kakra commented Jun 22, 2023

Maybe related to #211 or #117?

@MateusRodCosta
Copy link
Author

MateusRodCosta commented Jun 27, 2023

Just re-tried letting shaders compile in the background and it seems it succeded for A Hat in Time and a few other games without crashing.

It might have been fixed due to any update (I believe at least the Nvidia driver updated).

I will close this and if it re-appears I will reopen.

I will also try to open a new issue about the fact that there's no indicator that shaders are compiling on the new UI. Seems it already exists as ValveSoftware/steam-for-linux#9405.

@MateusRodCosta MateusRodCosta closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2023
@MateusRodCosta
Copy link
Author

Reopening.
It seems the problem is not so much the fact that the shader compilation never completes... (I actually let all games have their shaders processed a while ago)
The problems seems to be that on every new Steam launch it will want to check the compiled shaders and for the same few games it wants to do the processing all over again.

From the logs the games that it seems to happen the most (and it's the most noticeable because they have the most shaders) are:

  • A Hat in Time
  • Skyrim: Special Edition
  • Dragon's Dogma: Dark Arisen

This is a bit annoying, because if I decide to play, say, A Hat in Time, I have to wait for hours for the shader processing again, which is kinda the reason I enabled background processing, to avoid waiting so much.

Attached new logs:

shader_log.txt
shader_log.previous.txt

@jpakkane
Copy link

This also happens on AMD Radeon RX 6600 (navi23, LLVM 15.0.7, DRM 3.49, 6.2.0-27-generic) (0x73ff) using Kubuntu 04/23. Steam installed via Flatpak.

I haven't tried to let it finish, I just click skip to get to play the game within a reasonable time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants