Open weirddan455 opened 3 years ago
I already thought I was alone with that issue. For the time being I have also switched to opengl.
https://github.com/ValveSoftware/Dota-2-Vulkan/issues/381
From my involuntary testing the crash can happen at any moment (in game, in the menu, during start of the game..) and happens quite frequently, but isn't immediately reproducible.
I'm having this issue as well, Started quite recently and now almost reliably crashes every game, especially in the first couple of minutes.
Arch, GTX 1060 3GB
[50923.748454] GlobPool/1[47468]: segfault at 60 ip 00007f56a987ae06 sp 00007f56aadede30 error 4 in libnvidia-glcore.so.465.31[7f56a86fd000+11c7000]
[50923.748472] Code: 24 90 00 00 00 e8 aa f8 ff ff 49 8b 96 c0 00 00 00 48 be ff ff ff ff ff ff ff 3f 48 8b 92 f8 02 00 00 4a 8b 84 3a 90 01 00 00 <48> 23 70 60 48 8b 83 30 01 00 00 48 01 f0 48 89 43 10 41 8b 86 dc
I'll give OpenGL a try.
Started quite recently
Interesting, I have had that for months. Can you think of anything you changed that could have trigger it? My first report was with 455, but I think I have had that even with older versions before that.
Sorry, I should have written this in my post above, I just recently started playing Dota again (since the beginning of the month), but I haven't had any crashes in the first few days. They sporadically started after a few days and then gradually increased to at least one every game.
I just played a few matches with OpenGL and had no crashes either. Unfortunately, the performance with OpenGL is noticably worse though.
Your system information
Steam
->Help
->System Information
) in a gist:Please describe your issue in as much detail as possible:
GPU: Nvidia GeForce 770 GTX 2GB Distro: Arch Linux Dota seems to randomly lock up and crash when using the Vulkan renderer. I went several games without any crashes and then crashed 3 times in a single game. I switched to the OpenGL renderer and haven't had any futher issues. I logged the following crash message from dmesg (identical for all 3 crashes):
Steps for reproducing this issue:
I don't have a way to reliably reproduce this, unfortunately.