Open ghost opened 4 years ago
Same for me, the console reports: teamNetworkingSockets lock held for 7.6ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.8ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.3ms. (Performance warning). SendMessageToConnection Waited 2.1ms for SteamNetworkingSockets lock [ServiceThread] SteamNetworkingSockets lock held for 9.4ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection Waited 2.3ms for SteamNetworkingSockets lock [ServiceThread] SteamNetworkingSockets lock held for 7.2ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 8.3ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 7.2ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 7.5ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection 0: Reinitialized 4 predictable entities
Same for me, the console reports: teamNetworkingSockets lock held for 7.6ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.8ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.3ms. (Performance warning). SendMessageToConnection Waited 2.1ms for SteamNetworkingSockets lock [ServiceThread] SteamNetworkingSockets lock held for 9.4ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection Waited 2.3ms for SteamNetworkingSockets lock [ServiceThread] SteamNetworkingSockets lock held for 7.2ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 8.3ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 7.2ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 7.5ms. (Performance warning). SendMessageToConnection SteamNetworkingSockets lock held for 9.6ms. (Performance warning). SendMessageToConnection 0: Reinitialized 4 predictable entities
Having the same issue. Console shows the same errors over and over again in red. I tried verifying the game files, but that didn't change anything.
The same thing happens to me, it is impossible to play, I have not found any solution anywhere
https://www.youtube.com/watch?v=plD3-bg62oM voy a probar con este video, los comentarios son positivos
From the small sample of servers I've played on I noticed it seems to happen only Valve official servers.
It doesn't happen in at least some of the community servers.
Hope this info helps.
This happens on all servers for me, tested with a VPN too, same issue.
Anyone found a solution?
From the small sample of servers I've played on I noticed it seems to happen only Valve official servers. It doesn't happen in at least some of the community servers.
Hope this info helps.
Could you provide a specific server that does works? I seem to be having the problem on all servers I tried.
Could you provide a specific server that does works? I seem to be having the problem on all servers I tried.
Yes. I'm not experiencing any networking problem on Banana's retake servers for example : 49.12.128.124:27002
I can confirm this issue on MM servers and there weren't any when I played on Windows. (same pc/hw, same connection)
Banana's retake servers for example : 49.12.128.124:27002
I have lag on this server too.
Things I tried and didn't work:
All with no luck. On my Windows 10 there are no problems at all on the same machine.
This is an absolute bug in the CS:GO client for Linux.
The problem sounds to be solved both today and yesterday, I am getting normal ping at 60 again.
Was there any change from Valve's servers? I wonder.
Last update still hasn't fixed this issue for me.
I still get spammed with the error message and the skipped frames are still here.
As I mentioned before, this is happening in competitive matches. Probably I should quit playing.
The same problem has been reported on the /r/globaloffensive subreddit : https://old.reddit.com/r/GlobalOffensive/comments/ix9u7l/my_console_keeps_getting_spammed_with_the_same/
OP runs on Windows 10.
I'm having this issue on Ubuntu 20.04
Same issue on ArchLinux, kernel 5.8.1, game version (by net graph) 1181. I am getting a lot of SteamNetworkingSockets lock held for ~11ms. There is not a huge difference in quality of experience.
Another post on /r/globaloffensive : https://old.reddit.com/r/GlobalOffensive/comments/j4w99i/waited_724_ms_for_steamnetworkingsockets_lock/
I get the bug on both windows and linux, it seems like it is not an OS problem.
I just would like to add that I face the same issue for months now. The output from my Steam system info
If more info is needed, please let me know
This still happens. i just hopped into deathmatch today to take a video of it cause I noticed it yesterday. It'd seem the issue comes from the server var being very high. I asked other people in the lobby and they said it was really laggy for them too. Isn't step 1 of running a cs:go server having enough resources to run a cs:go server? :/
PLEASE FIX THIS!
This doesn't seem to be Linux-exclusive, as I'm experiencing it on both Windows 10 and Arch Linux.
These errors are spamming my console but I'm not experiencing any lag as depicted in the gifs.
Seeing this as well, for weeks already. Running through gamemode. Tried to disable other network devices/interfaces, didn't seem to help.
Reinstalling the game made it 3x worse for me (I'm on Win10). It's making the game unplayable and Valve just seems to not care.
Same issue here. MM is unplayable due to 'SteamNetworkingSockets lock held'. I am using archlinux kernel 5.8.14-arch1-1
The DM-issue and 'SteamNetworkingSockets lock held' are completely separate issues. I have DM-issue on both Windows and Linux which I assume is more to do with servers as other players complain too. The SteamNetworkingSockets-issue on my system is only on Linux; may have to do with packet offloading? I've tried console settings net_maxroutable to 576 and net_splitrate 100 (absurdly high, just a guess number) and I think I see less problems with the lock. The lock is held 10+ ms still though which is really making gameplay impossible.
Here is my network adapter config from Windows. if you try these make notes of your previous config:
arp offload : enabled flow control : disabled interrupt moderation : enabled ipv4 checksum offload : disabled jumbo frame : disabled large send offload v2 ipv4 : disabled large send offload v2 ipv6 : disabled ns offload : disabled priority & VLAN : both enabled receive buffers : 512 speed & duplex : 100 Mbps Full tcp checksum offload (ipv4) : disabled tcp checksum offload (ipv6) : disabled transmit buffers : 128 udp checksum offload (ipv4) : disabled udp checksum offload (ipv6) : disabled wake on magic packet : disabled wake on pattern match : disabled wol & shutdown link speed : 10 Mbps first
I've tried emulating it on Linux with ethtool , but no success. I think this SteamNetworkingSockets thing has to do with how cs:go is using the api, something is blocking progress inside the lock... maybe waiting for packets even.
So I've SteamNetworkingSockets lock held on my Pop!_OS 20.04 LTS install for the last few months as well. Only happens when I play on Valve server (MM, DM, watching a MM game). An hour ago I've tried 3 things at the same time, and it seemed to have helped a lot:
Set net_maxroutable to 576 and net_splitrate to 100, as per LennyBruh
Disable steam overlay
Add -threads 3 to my launch options (I have a CPU with 4 cores, 4 threads, so 1 less than that is set.)
I might try to find out which combination of those settings did it exactly. But basically now I don't get the lock held messages in the console, and my game feels a lot smoother in a MM game.
Side notes:
I've kept net_client_steamdatagram_enable_override 1 from a previous attempt to fix this.
uname -a: Linux pop-os 5.9.0-8.2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.9-4ubuntu1~focal (2020-11-11) x86_64 x86_64 x86_64 GNU/Linux
@spider3000 these property changes don't seem to change anything in my case. There's possibly a wider set of issues that is causing these error messages.
@spider3000 @timvisee I also just tried using the proposed properties but had no luck. I still got the same network issue massages and lags.
@andresilva97 This does not solve the problem, the only thing it does is hide the messages.
still getting these errors
When are you guys going to realize that CS:GO on Linux is treated as a second-class citizen? :)
They still haven't fixed this simple bug for more than a year.
When are you guys going to realize that CS:GO on Linux is treated as a second-class citizen? :)
Multiple people said they had the issue on windows.
Additional observations in past weeks :
I always have the error messages in the console on Valve servers but seem to be suffering from the "lag" only when there are more than 10 players in the server. For example I have minimal lag in comp and retakes, bad lag in casual and unplayable lag in "danger zone".
By "unplayable lag" I mean player models updating their position every half a second, teleporting 1.5 meter at a time.
When are you guys going to realize that CS:GO on Linux is treated as a second-class citizen? :)
Multiple people said they had the issue on windows.
Additional observations in past weeks :
I always have the error messages in the console on Valve servers but seem to be suffering from the "lag" only when there are more than 10 players in the server. For example I have minimal lag in comp and retakes, bad lag in casual and unplayable lag in "danger zone".
By "unplayable lag" I mean player models updating there position every half a second, teleporting 1.5 meter at a time.
When it happens to me other peope in the server are also complaining about it. It's because step 1 of running a cs:go server is having enough system resources to run the cs:go server and the server var is always really really high when this issue happens. This will likely never be fixed because it actually costs money instead of just someone who is already paid to be there fixing a bug Which already almost never happens with any of the bugs posted here anyway.
Same issue here - game was playable for months - until recently. SteamNetworkingSockets lock held
messages all over the place and very laggy experience. Please fix!
OS: Fedora 33 CPU: i4770 GPU: Radeon RX 580 RAM: 16GB
This bug has been fixed for me. I’m on Arch Linux. This might actually be a bug in a system lib somewhere and not in the game.
This might actually be a bug in a system lib somewhere and not in the game.
Don't think so. I'm also on Arch and this message is still spammed no matter what game mode you play:
https://www.youtube.com/watch?v=ot_xk1Px8J8
If I reboot to my Windows 10 installation though, I get no such message.
Heh, just noticed a different bug in this video. I had Deathmatch selected, but once I clicked "GO", it changed the game mode to Casual. Lovely.
@guihkx I must have disabled a setting or flag somewhere then. I do have a heavily tweaked system.
Well, if you do find out, please let me know. I'd be happy to give a try.
FWIW, I also have CS:GO installed on Flatpak'd Steam (CS:GO font rendering is so much better there than the "official" Steam package provided by Arch Linux, by the way), and this issue is also present there.
This SteamNetworkingSockets lock held for X.Xms. (Performance warning).
message comes from this open-source library by Valve:
But it's network-related and too low level, so I have no idea what could trigger it, so perhaps it would make sense to open a new issue there asking for a "user-friendly" explanation from the devs.
I believe this has been fixed as of today's CS:GO update 1.37.8.5.
Although, I think OP's issue might not be exactly related to the SteamNetworkingSockets
message, so who knows.
Please test away, guys! :)
Nope, problem is still there. Restarting the game didn't help me, so i have to find the solution while playing ranked match. FPS drops when i spectate other players, when i open scoreboard in the game, or turn on voice chat.
@theheartbenvn That's on Windows though, right? Anyway, just a guess here but have you checked if you have your Power Plan set to Power saver? Also, make sure you have Multicore Rendering enabled in CS:GO's video settings. And on an unrelated note, you may want to disable CS:GO's VSync as well if you have it enabled, as it adds input lag.
Hey, I've retested this issue on Casual, Deathmatch and Danger Zone Valve servers on a Ubuntu system.
What I experienced before the update :
SteamNetworkingSockets lock held for X.Xms SendMessageToConnection
DispatchAsyncEvent backlog, failed to dispatch all this frame. XXXX of XXXX remaining
To me the choppiness seemed directly correlated to the number of players on the server. The game is almost unplayable in the beginning of a Danger Zone rounds with models being updated very infrequently and sounds being played noticeably later then when they should. As players dies the choppiness gets reduced and disappeared however the error messages still got spammed.
What I experience after the update :
SteamNetworkingSockets lock held for X.Xms SendMessageToConnection
DispatchAsyncEvent backlog, failed to dispatch all this frame. XXXX of XXXX remaining
Overall the error messages are almost gone - got 2 in ~30 minutes of playtime - but the gameplay problem is the same and what I said before about the number of players still holds true. During the DZ game I had this message spammed >20 times in my console Tried to look up command use as if it were a variable.
but I guess this has nothing to do with this issue.
Here is the connection summary I got at the end of my Danger Zone game : https://gist.github.com/ArthurPons/1d1bbbbbeaec74c637ba6af0111ade4d I don't really know how to read it but everything seems ok.
@theheartbenvn That's on Windows though, right? Anyway, just a guess here but have you checked if you have your Power Plan set to Power saver? Also, make sure you have Multicore Rendering enabled in CS:GO's video settings. And on an unrelated note, you may want to disable CS:GO's VSync as well if you have it enabled, as it adds input lag.
I've already got almost everything set to what you've said, apart from my Power Plan being set to Power Saver. I don't really understand that choice.
I've already got almost everything set to what you've said, apart from my Power Plan being set to Power Saver. I don't really understand that choice.
My bad, I actually meant to say that you shouldn't have your Power Plan set to Power saver. Either 'Balanced' or 'Performance' should be fine.
I had this message spammed >20 times in my console
Tried to look up command use as if it were a variable.
I just got into a DZ match to check this. For me that message shows up every time I press Tab on my keyboard. It might not be exclusive to Linux too...
I've already got almost everything set to what you've said, apart from my Power Plan being set to Power Saver. I don't really understand that choice.
My bad, I actually meant to say that you shouldn't have your Power Plan set to Power saver. Either 'Balanced' or 'Performance' should be fine.
Well then i've already done all of it from before you told me to do so, yet i still encountered the issue.
Yeah, I'm not sure what it can be then... Could be your PC specs, maybe? CPU bottleneck? Some antivirus interfering with CS:GO? Judging by your screenshot, your var
seems pretty high too.
Sorry it looks bad. Only way to make it fit and embed