Open gardotd426 opened 3 years ago
kisak-valve
commented
3 years ago Hello @gardotd426, this is similar to some of the feedback on #6811, where one of Steam's worker tasks can outlive the main window. Instead of Fossilize replaying shaders like that issue report, in this case it's the worker task that is finding appropriate shader pre-cache datasets for your system. The same subcomponent mentioned in #8114.
gardotd426
commented
3 years ago @kisak-valve ah, that might explain why I've been seeing issues related to #8114 as well. Namely that I'm constantly getting a wineprefix update window for ~/.steam/root/steamapps/compatdata/0/pfx whenever Steam is open. After I launch any Proton game I get several wineprefix update windows for the 0 appid prefix, lasting several minutes. It just took 6 or 7 minutes for the last round to finish.
Zorgodon
commented
7 months ago Still not fixed! Need to run pkill -9 -f steam to get it to close after enabling proton for all titles and 'restarting'.
pfirsich
commented
3 months ago Not sure if that is the same issue, but for me the process keeping steam from exiting is explorer.exe (C:\windows\system32\explorer.exe /desktop). For me this process is using 100% CPU while steam is running (which makes Steam not very usable for me at the moment) and when I try to close it, steam does not disappear from the tray until I kill that process.
kisak-valve
commented
3 months ago Hello @pfirsich, that reads like a misbehaving compatibility tool. Can you tell which tool is the parent of that process? I'd use htop in tree view to find that information.
pfirsich
commented
3 months ago I wanted to make that collapsible, but the code block stops working if I do it. I can replace it with a file attachment if that's better as well.
kisak-valve
commented
3 months ago /home/joel/.local/share/Steam/steamapps/common/Proton 9.0 (Beta)/proton run /home/joel/.local/share/Steam/ubuntu12_32/../bin/d3ddriverquery64.exe is the process to focus on there. It's supposed to be a short lived test to figure out what that render path goes through. Somewhere between that, Proton 9.0, and your Vulkan driver it's getting stuck.
pfirsich
commented
3 months ago @kisak-valve That process looked weird to me too, because I see it constantly. When I run it manually it terminates after < 1s with exit status 1:
$ env STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/joel/.local/share/Steam STEAM_COMPAT_INSTALL_PATH="/home/joel/.local/share/Steam/steamapps/common/Proton - Experimental" STEAM_COMPAT_DATA_PATH=/home/joel/.local/share/Steam/steamapps/compatdata/1493710/ /home/joel/.local/share/Steam/steamapps/common/Proton\ 9.0\ \(Beta\)/proton run /home/joel/.local/share/Steam/bin/d3ddriverquery64.exe
Proton: Upgrading prefix from 9.0-201 to 9.0-200 (/home/joel/.local/share/Steam/steamapps/compatdata/1493710//)
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.I am using a laptop with a dedicated nvidia MX150 gpu and intel integrated graphics. This is my mesa-vulkan driver:
mesa-vulkan-drivers/jammy,now 24.0.3-1pop1~1711635559~22.04~7a9f319 amd64.
And this is my NVIDIA driver: nvidia-driver-550/jammy,now 550.67-1pop0~1710948064~22.04~b0f6b1b amd64.
I have not installed your mesa-drivers, because I hoped it would use the MX150 anyways, but maybe something is going wrong there.
Is there some information I could provide or things to try that could help fix this issue? Does my issue still fit into this github issue or should I open another?
pfirsich
commented
2 months ago After an update and restarting the issue has disappeared.
Your system information
Please describe your issue in as much detail as possible:
After today's Steam Client Beta update, Steam crashes when attempting to exit the application. I click "exit," the tray icon stays (and steam is still running, only the window has closed), and it takes about 2-3 minutes before it finally exits.
Running Steam from the terminal so I can see the logs indicates there's some sort of crash that happens when I try to exit. Here is the output to the terminal after I click "Exit":
Thread "CJobMgr::m_WorkThreadPool:2" (ID 6548) failed to shut downjust repeats every few seconds until I either kill the process manually, or it finally shuts down after a few minutes of waiting.When I re-launch Steam after it finally shuts down, I see a bunch of this in the terminal:
And then the process repeats. All games and whatnot are working as always.
Steps for reproducing this issue: