pak01*.vpk was never closed

[lfry512]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: https://gist.github.com/lfry512/a0717109cc6506a2e1fd20daf8a9059b
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Every so often, after entering a game, the FPS will drop very sharply and the game becomes unplayable. As I monitor the output of steam on the console, I notice that this happens when I get messages like this: File /home/user/.steam/steam/steamapps/common/Counter-Strike Global Offensive/csgo/pak01_040.vpk was never closed

I get about 50-100 of them. It used to not happen so often but now it happens almost all the time following the Shattered Web update. My suspicion is that memory is not released when this happens, which in turns affects the frame rate. This might not have been an issue for others in the past if they have much more RAM and video RAM than I do.

Steps for reproducing this issue:

1. It seems to occur at random, I have no idea what triggers it. It also happens much more often following the Shattered Web update.

Any ideas on how to debug or even fix this?

[pbhj]

AFAIK I've had this error appear since forever (at least since the Panorama update to my recollection). Just assumed it was benign since it doesn't appear to be related to slow-downs for me (but my FPS is generally low, because potato).

[lfry512]

Thanks @pbhj !

Over the last few weeks I have been trying to observe more closely the behaviour of the game so I can clarify:

Before the Shattered Web update, I had perfectly fine FPS and rarely I would face the issue described above. I could restart CSGO and steam and everything would be fixed. I use to see only one message for each pakX_Y.vpk message.

Now I observe two messages for each pakX_Y.vpk, a detail that I didn't specify in my original post.

Steps for reproducing the issue:

1. The first game works normally after starting steam then CSGO, only if:
   • The map doesn't change while loading.
   • The following doesn't happen: For some reason a different map is sometimes displayed before showing the correct map, even just after starting steam, then CSGO and then joining a competitive game where a single map is selected, or joining Dust II deathmatch or casual.
2. The second game will have a notable drop in FPS. Also friends I have played with have said that I appear to be lagging/glitching ingame suggesting this isn't just graphics related.
3. The issue never occurs if the first game works and I never play a different map in subsequent games (Dust 2 servers). However I still get two messages per .vpk file in this case.
4. On some specific aim map community servers I have managed to play several games without this issue.

In conclusion I am not at all sure this issue is related to the .vpk messages, it just raises my suspicions that something is not being closed/freed, and it 'feels' like it's correlated to what I am seeing ingame.

I will hopefully get actual data on the csgo process, like how much memory/cpu it is using when the game is working vs when it is not. Generally I don't look when it is working as I am trying to have fun and use the opportunity!

[csgo-react]

I'm not sure if it is exactly the same issue but had something similar after Panorama update. After some point of playing fps dropped down from 140+ to less than 30. Can't tell you exact numbers anymore but it was unplayable. I made some break playing CSGO at linux because of this. In last months I tried it again and it did work again. However in trials of fixing another issue recently I noticed I also have 'pak01_***.vpk was never closed' (82 times in total) after/while closing CSGO. Above this pak01 issue console prints "Leaking 2021 vertex shaders Leaking 7236 pixel shaders" which sounds like a memory leak as well. You have this too?

As far as I remember it also happened at the first map if the game took some time (cs_office). I think rejoining the game (exit steam, start steam again and csgo) did not fix this issue (but very uncertain about this). You can check out if this solves the low fps or not. That might be some valuable information for finding the bug.

I thought valve did some fix with an update. Can't remember doing any special change at my PC. Only thing I remember is a driver update for nvidia driver. Your system info shows version '390.116'. I have a more recent version '410.73' (exact version might be different for your distribution)

Not sure if it helps but may be worth a trial.

[biletnikov]

I have this issue on the Linux server (Debian 10). The server works fine after pure installation but in some days or weeks I havve this issue. The server can not be started and it is in restarting loop for every 10 seconds.

[allegfede]

got the same from the "basalt" client update ..... ubuntu 20.04 64bit - nvidia gtx 950 gpu on an i7 4770s with 8GB of ram from 340fps to 24 or less .... a lot of " .....vpk was never closed"

[KenTheWhaleGoddess]

+1, on Steam Linux Runtime 1.0 Kernel: 6.2.0-32-generic Linux Mint