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
Dota 2 hangs when closing - Arch Linux / Nvidia Proprietary Drivers / Vulkan #1992
Comments
I'm experiencing the exact same issue. kill -9 DOTAPID will close the program or killing all steam processes. Otherwise the process will not close. My setup is similar to the user above Arch, Nvidia, Vulkan. |
It's probably worth noting that the |
The issue disappears when I roll back to nvidia-470xx using: |
Just to add that it's not Arch exclusive. Happens the same thing on Fedora (35 in this case) |
OK, looks like it's the same as ValveSoftware/Dota-2-Vulkan#392 |
This happens to me as well using Vulkan (everything is fine on openGL) on EndeavourOS with up-to-date nvidia drivers. System Information Gist pulled from steam. |
I looked over your SysInfo Gist @jakepacheco and it looks like you're on the 495 nvidia drivers. I rolled mine back to 470 and haven't had any issues. Same on elementaryOS 6 Odin and Manjaro. |
Can reproduce this bug using nvidia 495 drivers and the vulkan backed on NixOS. |
The same for me, I use Manjaro with nvidia 495.44 |
Same here, Ubuntu 20.10, nvidia driver 495. |
I'm also having this issue, started immediately after switching from 470 to 495 drivers. Running Manjaro KDE with vulkan |
Can reproduce on Ubuntu 21.10 with nvidia 495.44 |
Same with nvidia 495.44 Arch Linux on Zen kernel |
Definitely related to the 495 driver, can confirm this issue. |
Ubuntu 20.04 with nvidia 495.44. Exact same issue |
I'm on Manjaro with 5.15.2-2 kernel, nvidia 495.44 drivers, and also have the same issue. An annoying but simple workaround is alt-tab and stop the game in Steam using the big blue Stop button in the library. |
Backtrace from gdb attached. The hang only happens when Vulcan is enabled, OpenGL doesn't show an issue. However, with OpenGL, the initial screen with Aghanim causes the GPU to peg at 100% and causes the rest of the system to lag. Switching to a different screen (e.g. user stats) makes the GPU drop to about 10%. That problem doesn't happen with Vulcan (about 30% GPU on my system, GTX 1070 Ti). Hard to make much of the backtrace without symbols. Maybe a race condition in vkDestoryDevice or some issue in the libGLX_nvidia.so library? |
@nascheme I have the same issue with GL, so I have disabled the Aghanim's dashboard entirely, see: https://www.reddit.com/r/DotA2/comments/rkyk50/how_to_disable_the_dashboard_cinematic_entirely/ |
I don't have an issue on hanging with closing, but the game is unplayable on 495 drivers. I have a 3090 and 5900X and the game is constantly freezing for about 10 seconds. It'll do it every 5 or 10 seconds and then pick up again, and run at the full 240 fps, but then freeze again. |
Same here with nvidia 495.46, but if I recall correctly the same thing happened on my previous laptop with intel drivers and OpenGL. |
Experiencing this issue with
Any tips for rollback in the meantime? nvidia-settings doesn't seem to make switching drivers trivial. Is it as simple as reinstalling mhwd-nvidia-470xx (from AUR)? |
I was having the same issue, but seems to be fixed with either nvidia 510.39 or a game update |
Yup - the nvidia 510.39 driver fixed it (arch [with paru] EDIT:
|
I can also confirm that the 510.39 driver fixed it for me (Debian testing distribution). I can run with Vulkan enabled now. I didn't re-enable the Aghanim animation on the home screen but I suspect that's fixed too (in terms of using 100% GPU). The framerate in game seems decent with Vulkan enabled, bottleneck still seems to be the CPU. BTW, the 510.39 driver fixed my issues with Firefox video acceleration as well. Previously Youtube videos played in Firefox would cause the UI to drag. So, whatever Nvidia has done seems to have fixed some things, not just Dota 2. |
Please how to install NVIDIA 510 drivers on Ubuntu? Actually I have laptop with nvidia optimus technology so I cannot install manually the latest drivers. Have to wait I guess for the official ubuntu version :/ For now I have to kill it manually with the command below
|
where can you download nvidia 510 from ? |
@pilak @qw34ty Honestly if you're on Ubuntu I would just wait until 510 comes out of beta and is available in the Part of using Ubuntu means not having access to the latest software, it's a static release distribution. 510 is a beta driver, it's not in any distribution's repos (it's in the AUR but it is not in the Arch repos). Most people using 510 are likely going to be on distros like Arch or Manjaro where they can install the driver through the AUR or use a community repo like |
@gardotd426 problem with PPA drivers is that they not including the 32-bit compatability libraries which breaks steam dependencies, and when you apt install the 32-bit lib, it removes the 64-bit libs, so installing the .run file like this was the only way i could get it working, currently on 495. |
Dont think that game update does anything here, my install of steam + dota2 was done few days ago. |
Hello @qw34ty, your claim about PPAs is generally not true. It's specifically NVIDIA's third party repository for their CUDA driver, which is outside the launchpad PPA system, that does not provide 32 bit packages. Ubuntu's main repositories and https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa do have the packages. |
Tried both of those PPA's the ubuntu offical had such poor performance was unusable, and the NVIDIA was broken as mentioned above. |
@kisak-valve the That's the launchpad package information for
@qw34ty This isn't true at all. Again, look at the screenshot. That's from the |
Confirmed, no longer hangs on updated driver version 510.47.03. I think it's safe to close this for now. |
confirmed this is still an issue 1min+ loading and closing time.
|
Same here. In Arch Linux with nvidia-beta 510.47.03-1 Dota 2 still hangs when closing. |
Ubuntu 21.10 with the 510 driver and the game no longer hangs for me. RTX 3070 |
My laptop has a dual GPU, an AMD GPU, and an NVIDIA RTX 3060. I'm running Dota 2 with |
this has been fixed for me upgrading manjaro to 5.16.5 kernel + 510 drivers |
I don't have any issues with driver version 510.47.03. I usually play with the OpenGL render but Vulkan seems to work okay too. The GPU utilization seems about the same between -gl and -vulkan. I installed the drivers using the NVIDIA installer, using the |
for me did not work upgrade kernel version |
Where can we get any additional information for why this is so slow ? it's basically under-performing my onboard ryzen3400g integrated graphics (on low settings). |
the problem is now solved with drivers 510 but I agree with @qw34ty that the game has very much freeze phase always at the same place I mean when loading heroes page for draft. it's noticeable because I often don't have time for ban phase EDIT: the problem does exist for years. but at start it was not that impacting. updates after updates the game is more and more slow (do you have stocks in Intel, AMD, etc ? :)) ) |
@pilak Solved for you maybe, not for me. |
Your system information
System information from steam (
Steam
->Help
->System Information
) in a gist:systemsettings.txt
Have you checked for system updates?: [Yes/No]
Are you using the latest stable video driver available for your system? [Yes/No]
Have you verified the game files?: [Yes/No]
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.
When I try to close Dota 2, I get the "are you sure..." prompt, I click "Yes", but the game never quits: the screen just sits there and does nothing. I'm forced to open System Monitor and kill the dota2 process in order for it to close.
Launch options: -sdl_displayindex 0 -phased_window_create
Using Vulkan renderer, latest Nvidia proprietary drivers,
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: