Linux Frame rate drops. Stuck on around 10-15 FPS until i leave and rejoin. Caused by team fights and specific heroes?

[kqr]

I've had issues with deadlock dropping frames and not picking them up again since i switch to linux (mint) a couple weeks ago. Since the previous update the drops have been inconsistent - some games go without any issue, and others have issues. In the games it has issues it happens multiple times a game.

I have never had this happen in the laning stage, and when the frame drops start it seems to be during a team fight. As it doesn't happen every game I think it might be due to some heroes but I'm not too sure.

Previous issues I had involved FPS drops at 30 minutes (consistently) and more consistent frame drops, but since this update it has seemly changed a little bit. The only command/launch option I have is "-no_prewarm_map". I used to have "-LD_PRELOAD="" %command%" but stop using it as it wasn't solving the issues I had previously but since the new patch I haven't tried it - I'll do that tmr

I'll try to update the games where I do and don't get lag spikes - you will be able to tell when I lag out when I (kqr) dc from the game. I will try to link time stamps in future. (dd/mm)
Games with lag spikes;
39590102 (25.8)
39847287 (27.8), 2 instances, one was mid boss dying. not sure for other one
39849886 (27.8), few instances. Was connected with spikes in MS - would go to 300 then down to 50-80 and maintain a poor FPS. rejoin works to fix it

Games without lag spikes;
39592247 (25.8)

 

[brokebrains]

I have the same issue running on Linux with an RTX 2060 Super, driver version 575.64.05. In my case it looked like some kind of VRAM leak, you can use the command "cl_showmem 3" to display the current VRAM usage and watch it over the course of a game. It seemed like certain abilities during teamfights would commit more and more VRAM that never gets freed up again, so over the course of a game I'd eventually use up all 8GB and drop from 90-100fps down to under 20. The issue is present using both native Vulkan and DX11 (DXVK).

The bandaid fix for me was simply dropping texture quality down to medium, freeing up a couple of gigabytes and basically resolving the issue for now. I assume the leak is still there, but there's enough headroom that it doesn't crop up even after multiple games.

Interestingly, on Windows I can see a similar effect where the VRAM usage steadily creeps up, but Windows actually frees up memory in time and I couldn't reproduce the problem, even using high textures. I just have no idea if this is a Linux/Proton issue, an NVIDIA Linux driver issue, or an issue with Deadlock itself.