ReceivingUncompressedUpdateFromServer
commented
1 year ago Screenshots
Open ReceivingUncompressedUpdateFromServer opened 1 year ago
ReceivingUncompressedUpdateFromServer
commented
1 year ago Screenshots
[Client] CL: Receiving uncompressed update from server
It happens at the start of every match. About 12 seconds into the picking phase "[Networking] NetChan client ProcessMessages" starts sending thousands of messages like PacketStart and PacketEnd over and over. AS SEEN BELOW. Causing eventual disconnections and Low Priority penalty from failure to reconnect.
If able to reconnect (infrequently), the game runs fine without issue. Normal. The issue is strictly the Receiving uncompressed update from server , about 30s period of time during the picking phase.
I have Google Searched over 10 pages back for "Receiving uncompressed update from server". I have made a new Dota Account. I have reinstalled Dota. I have reinstalled on newer OS (win 10) from Win 8.1. I have installed a new SSD. I have even changed residences twice meaning its not to do with my location.
Nothing works bc i suspect it is Valve's cancer and has nothing to do with my setup. Is there anyone who can offer any insight? Observe the issue for yourself, below (Notice the NetChan Spam)
[Client] CL: Receiving uncompressed update from server LoadFullBodyLoadoutPortraitInfo failed to load scripts/npc/portraits_full_body_loadout.txt! [Networking] NetChan client ProcessMessages has taken more than 630ms to process 860 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 880 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 900 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 920 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 940 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 960 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 980 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1000 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1020 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1040 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1060 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1080 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1100 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1120 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1140 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1160 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1180 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1200 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1220 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1240 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1260 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1280 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1300 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1320 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1340 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1360 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 630ms to process 1380 messages. (Current message type: 'CNETMsg_Tick [4]') [SteamNetSockets] SteamNetworkingSockets lock held for 5.7ms. (Performance warning.) ServiceThread,RecvUDPPacket(x955),CSteamNetworkConnectionBase::Think,SNP_SendPacket,SendUDPacket,PostConnectionStateUpdateForDiagnosticsUI,SteamDatagramClientThinker::Think,EnsureDataCenterRoutesValid,ThinkPingProbes,ThinkSelectServer This is usually a symptom of a general performance problem such as thread starvation. [SteamNetSockets] [#2541504226 SDR server steamid:90175843018185738 vport 0] recv queue overflow 1000 messages already queued. [SteamNetSockets] [#2541504226 SDR server steamid:90175843018185738 vport 0] problem detected locally (5002): Reliable message size 9 too large for remaining space in message queue. [SteamNetSockets] SteamNetworkingSockets lock held for 38.7ms. (Performance warning.) ServiceThread,RecvUDPPacket(x3820),PostConnectionStateUpdateForDiagnosticsUI,SendUDPacket(x812),CSteamNetworkConnectionBase::Think,SteamDatagramClientThinker::Think,EnsureDataCenterRoutesValid,ThinkPingProbes,ThinkSelectServer This is usually a symptom of a general performance problem such as thread starvation. [Client] CL: Receiving uncompressed update from server LoadFullBodyLoadoutPortraitInfo failed to load scripts/npc/portraits_full_body_loadout.txt! [Networking] NetChan client ProcessMessages has taken more than 255ms to process 500 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 520 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 540 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 560 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 580 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 600 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 620 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 640 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 660 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 680 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 700 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 720 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 740 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 760 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 780 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 800 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 820 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 840 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 860 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 880 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 900 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 920 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 940 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 960 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 980 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1000 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1020 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1040 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1060 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1080 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1100 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1120 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1140 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 255ms to process 1160 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1180 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1200 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1220 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1240 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1260 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1280 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1300 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1320 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1340 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1360 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1380 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1400 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1420 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1440 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1460 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1480 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1500 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1520 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1540 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1560 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1580 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1600 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1620 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1640 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1660 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1680 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1700 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1720 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1740 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1760 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1780 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1800 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1820 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1840 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1860 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1880 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1900 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1920 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1940 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1960 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 256ms to process 1980 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2000 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2020 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2040 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2060 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2080 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2100 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2120 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2140 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2160 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2180 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2200 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2220 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2240 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2260 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2280 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2300 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2320 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2340 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2360 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2380 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2400 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2420 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2440 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2460 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2480 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2500 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2520 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2540 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2560 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2580 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2600 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2620 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2640 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2660 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2680 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2700 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2720 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2740 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2760 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2780 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2800 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2820 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2840 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2860 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2880 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2900 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2920 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2940 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 257ms to process 2960 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 258ms to process 2980 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 258ms to process 3000 messages. (Current message type: 'NetMessagePacketStart [-1]') [Networking] NetChan client ProcessMessages has taken more than 258ms to process 3020 messages. (Current message type: 'NetMessagePacketEnd [-1]') [Networking] NetChan client ProcessMessages has taken more than 258ms to process 3040 messages. (Current message type: 'CNETMsg_Tick [4]') [Networking] NetChan client ProcessMessages has taken more than 258ms to process 3060 messages. (Current message type: 'NetMessagePacketStart [-1]') [GCClient] Recv msg 26 (k_ESOMsg_UpdateMultiple), 2077 bytes [NetSteamConn] Steam Net connection #2541504226 SDR server steamid:90175843018185738 vport 0 problem detected locally, reason 5002: Reliable message size 9 too large for remaining space in message queue. [Networking] Reliable message size 9 too large for remaining space in message queue. [NetSteamConn] Closing Steam Net Connection on socket 'client' to =[A:1:2456525834:24179], handle #2541504226 (0 (null)) [NetSteamConn] CloseSteamNetConnection handle #2541504226 (userdata 0) [NetSteamConn] Disassociating NetChan client =[A:1:2456525834:2417[0] (=[A:1:2456525834:24179]) from Steam Net Connection handle #2541504226 (userdata 0) [Networking] Summary of connection [#2541504226 SDR server steamid:90175843018185738 vport 0]: [Networking] End-to-end connection: closed due to problem detected locally, reason code 5002. (Reliable message size 9 too large for remaining space in message queue.) [Networking] Remote host is in data center 'eat' [Networking] Current rates: [Networking] Sent: 0.6 pkts/sec 0.2 K/sec [Networking] Recv: 348.7 pkts/sec 34.3 K/sec [Networking] Ping:613ms Max latency variance: 42.3ms [Networking] Quality: 100% (Dropped:0.00% WeirdSeq:0.00%) [Networking] Est avail bandwidth: 78.1KB/s
[Server] CNetworkGameServerBase::SetServerState (ss_waitingforgamesessionmanifest -> ss_loading)
[Server] CNetworkGameServerBase::SetServerState (ss_loading -> ss_active)
[Client] CL: CWaitForGameServerStartupPrerequisite done waiting for server
[Client] CL: CCreateGameClientJob creating client connection to 'loopback'
[SteamNetSockets] [#3810335878 pipe] connected
[SteamNetSockets] [#785816823 pipe] connected
[Networking] Created poll group for socket 'client'
[Networking] Created poll group for socket 'server'
[Networking] Connected loopback client=e31d1c86@loopback:1 <-> server=2ed69cf7@loopback:0
[NetSteamConn] Associating NetChan czn loopback:0[1] (loopback:0) with Steam Net Connection handle #785816823 (userdata 0)
[NetSteamConn] Associating NetChan client loopback:1[0] (loopback:1) with Steam Net Connection handle #3810335878 (userdata 1)
[Client] CL: Connected to 'loopback:1'
[Server] SV: Sending server info to client 'czn' at loopback:0, 6.1ms
[Server] SV: WriteInitialSpawnGroups sending 1 groups
[Server] Client 0 'czn' setting rate to 30000
[Client] Game: "Dota 2"
[Client] Map: ""
[Client] Players: 1 (0 bots) / 1 humans
[Client] Build: 9743 (revision 8294461)
[Client] Server Number: 4
[SignonState] CL: CNetworkGameClient::ProcessServerInfo
ReadSteamRemoteStorageFile( bufOut, "voice_ban.dt" ) -> 0.732554 seconds
[SteamNetSockets] SteamNetworkingSockets lock held for 21.4ms. (Performance warning.) SendMessageToConnection
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] Certificate expires in 46h46m at 1693552511 (current time 1693384122), will renew in 44h46m
[SteamNetSockets] SteamNetworkingSockets lock held for 200.0ms. (Performance warning.) ServiceThread,BeginFetchNetworkConfig,SteamDatagramClientThinker::Think,EnsureDataCenterRoutesValid,ThinkPingProbes
This is usually a symptom of a general performance problem such as thread starvation.
[Client] CNetworkGameClient::ProcessClassInfo: create on client true
[Client] CNetworkGameClient::ProcessClassInfo: creating client serializers from local server serializers (crc 0, server api exists)
[Client] Client missing networkable entity class CLightGlow
[Client] Client missing networkable entity class CNavLinkAreaEntity
[Client] Client missing networkable entity class CPhysMagnet
[Client] Client missing networkable entity class CSpotlightEnd
[Client] CNetworkGameClientBase::LinkClasses took 105.840 msec
[ResourceSystem] Failed loading resource "particles/water_impact/water_splash_01.vpcf_c" (ERROR_FILEOPEN: File not found)
[ResourceSystem] Failed loading resource "particles/water_impact/water_splash_03.vpcf_c" (ERROR_FILEOPEN: File not found)
[ResourceSystem] Failed loading resource "particles/water_impact/water_splash_02.vpcf_c" (ERROR_FILEOPEN: File not found)
[Client] CL: CGameClientConnectPrerequisite connection succeeded
ChangeGameUIState: DOTA_GAME_UI_STATE_LOADING_SCREEN -> DOTA_GAME_UI_STATE_DASHBOARD
[Client] LoadingDisplay changed from LOADING to NONE (map="")
[Server] SV: IGameSystem::LoopActivateAllSystems {
[Host] HO: IGameSystem::LoopActivateAllSystems {
[Host] HO: } IGameSystem::LoopActivateAllSystems done
[Server] SV: } IGameSystem::LoopActivateAllSystems done
[Server] SV: Game started
[Client] CL: IGameSystem::LoopActivateAllSystems {
ReadSteamRemoteStorageFile( bufOut, "scripts/control_groups.txt" ) -> 0.020136 seconds
[Client] CL: } IGameSystem::LoopActivateAllSystems done
[SignonState] CL: CNetworkGameClient::OnSwitchLoopModeFinished( game : success )
[GCClient] Send msg 7197 (k_EMsgGCMatchmakingStatsRequest), 8 bytes
Job CDOTALeagueShared::Reload has spent >3.000ms without yielding: 153.790ms
[Server] SV: Sending full update to client czn (reason: initial update)
[Client] CL: Receiving uncompressed update from server
[Networking] client loopback:1[0]: NetChan Setting Timeout to 30.00 seconds
[Client] CL: Signon traffic "client": incoming 80.626 KB [616 pkts], outgoing 3.502 KB [613 pkts]
[GCClient] Recv msg 7198 (k_EMsgGCMatchmakingStatsResponse), 326 bytes
Job CAsyncDataCache::RequestCurrentData has spent >3.000ms without yielding: 282.463ms
[Networking] czn loopback:0[1]: NetChan Setting Timeout to 20.00 seconds
[GCClient] Send msg 8673 (k_EMsgClientToGCRequestGuildData), 19 bytes
Job CAsyncDataCache::RequestCurrentData has spent >3.000ms without yielding: 32.134ms
Job CAsyncDataCache::BatchRequestData has spent >3.000ms without yielding: 494.154ms
Job CAsyncDataCache::RequestCurrentData has spent >3.000ms without yielding: 3141.890ms
[GCClient] Recv msg 8674 (k_EMsgClientToGCRequestGuildDataResponse), 19 bytes
Job CAsyncDataCache::BatchRequestData has spent >3.000ms without yielding: 4.982ms
ProtoBufHelper::ParseJSON: Ignoring extra JSON key 'success', which is not found in protobuf message 'CMsgDOTAPlayerInfoList'!
[SteamNetSockets] Waited 2.8ms for SteamNetworkingSockets lock
Job CAsyncDataCache::RequestCurrentData has spent >3.000ms without yielding: 3.709ms
[GCClient] Send msg 7197 (k_EMsgGCMatchmakingStatsRequest), 8 bytes
[GCClient] Recv msg 7198 (k_EMsgGCMatchmakingStatsResponse), 326 bytes
[Networking] Bytes buffered: 0 [Networking] Lifetime stats: [Networking] Totals [Networking] Sent: 1,908 pkts 375,639 bytes [Networking] Recv: 7,414 pkts 812,611 bytes [Networking] Recv w seq: 7,411 pkts [Networking] Dropped : 0 pkts 0.00% [Networking] OutOfOrder: 0 pkts 0.00% [Networking] Duplicate : 0 pkts 0.00% [Networking] SeqLurch : 0 pkts 0.00% [Networking] Ping histogram: (815 total samples) [Networking] 0-25 25-50 50-75 75-100 100-125 125-150 150-200 200-300 300+ [Networking] 0 0 0 773 14 6 6 5 11 [Networking] 0.0% 0.0% 0.0% 94.8% 1.7% 0.7% 0.7% 0.6% 1.3% [Networking] Ping distribution: [Networking] 5th 50th 75th 95th 98th [Networking] 76ms 81ms 87ms 101ms 188ms [Networking] Connection quality histogram: (9 measurement intervals) [Networking] perfect 99+ 97-99 95-97 90-95 75-90 50-75 <50 dead [Networking] 9 0 0 0 0 0 0 0 0 [Networking] 100.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% [Networking] Connection quality distribution: [Networking] 50th 25th [Networking] 100% 100% [Networking] Latency variance histogram: (7364 total measurements) [Networking] <1 1-2 2-5 5-10 10-20 >20 [Networking] 557 1596 3267 1356 320 268 [Networking] 7.6% 21.7% 44.4% 18.4% 4.3% 3.6% [Networking] Rate stats received from remote host 1.7s ago: [Networking] Sent: 200.9 pkts/sec 11.5 K/sec [Networking] Recv: 0.1 pkts/sec 0.1 K/sec [Networking] Ping:82ms Max latency variance: ???ms [Networking] Quality: 100% (Dropped:0.00% WeirdSeq:0.00%) [Networking] Bytes buffered: 0 [Networking] Lifetime stats received from remote host 0.5s ago: [Networking] Totals [Networking] Sent: 8,216 pkts 770,048 bytes [Networking] Recv: 1,103 pkts 143,360 bytes [Networking] Recv w seq: 1,102 pkts [Networking] Dropped : 0 pkts 0.00% [Networking] OutOfOrder: 0 pkts 0.00% [Networking] Duplicate : 0 pkts 0.00% [Networking] SeqLurch : 0 pkts 0.00% [Networking] Ping histogram: (807 total samples) [Networking] 0-25 25-50 50-75 75-100 100-125 125-150 150-200 200-300 300+ [Networking] 0 0 0 789 15 0 1 0 2 [Networking] 0.0% 0.0% 0.0% 97.8% 1.9% 0.0% 0.1% 0.0% 0.2% [Networking] Ping distribution: [Networking] 5th 50th 75th 95th 98th [Networking] 76ms 81ms 86ms 91ms 102ms [Networking] Connection quality histogram: (10 measurement intervals) [Networking] perfect 99+ 97-99 95-97 90-95 75-90 50-75 <50 dead [Networking] 9 0 0 0 0 0 0 0 1 [Networking] 90.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 10.0% [Networking] Connection quality distribution: [Networking] 50th 25th [Networking] 100% 100% [Networking] Latency variance histogram: (1089 total measurements) [Networking] <1 1-2 2-5 5-10 10-20 >20 [Networking] 812 146 84 47 0 0 [Networking] 74.6% 13.4% 7.7% 4.3% 0.0% 0.0% [Networking] Primary router: atl#109 (162.254.199.178:27031) Ping = 30+65=95 (front+back=total) [Networking] Current rates: [Networking] Sent: 1.4 pkts/sec 0.3 K/sec [Networking] Recv: 184.5 pkts/sec 21.6 K/sec [Networking] Ping:30ms Max latency variance: 42.0ms [Networking] Quality: 100% (Dropped:0.00% WeirdSeq:0.00%) [Networking] Bytes buffered: 0 [Networking] Lifetime stats: [Networking] Totals [Networking] Sent: 1,914 pkts 389,656 bytes [Networking] Recv: 8,257 pkts 878,666 bytes [Networking] Recv w seq: 7,445 pkts [Networking] Dropped : 0 pkts 0.00% [Networking] OutOfOrder: 0 pkts 0.00% [Networking] Duplicate : 0 pkts 0.00% [Networking] SeqLurch : 0 pkts 0.00% [Networking] Ping histogram: (8 total samples) [Networking] 0-25 25-50 50-75 75-100 100-125 125-150 150-200 200-300 300+ [Networking] 3 4 0 0 0 0 0 0 1 [Networking] 37.5% 50.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 12.5% [Networking] Ping distribution: [Networking] 50th 75th [Networking] 26ms 29ms [Networking] Connection quality histogram: (9 measurement intervals) [Networking] perfect 99+ 97-99 95-97 90-95 75-90 50-75 <50 dead [Networking] 9 0 0 0 0 0 0 0 0 [Networking] 100.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% [Networking] Connection quality distribution: [Networking] 50th 25th [Networking] 100% 100% [Networking] Latency variance histogram: (7331 total measurements) [Networking] <1 1-2 2-5 5-10 10-20 >20 [Networking] 689 1608 3114 1334 321 265 [Networking] 9.4% 21.9% 42.5% 18.2% 4.4% 3.6% [Networking] Rate stats received from remote host 1.8s ago: [Networking] Sent: 121.8 pkts/sec 15.2 K/sec [Networking] Recv: 0.9 pkts/sec 0.1 K/sec [Networking] Ping:30ms Max latency variance: 1.1ms [Networking] Quality: 100% (Dropped:0.00% WeirdSeq:0.00%) [Networking] Bytes buffered: 0 [Networking] Lifetime stats received from remote host 0.5s ago: [Networking] Totals [Networking] Sent: 8,256 pkts 878,592 bytes [Networking] Recv: 1,105 pkts 144,384 bytes [Networking] Recv w seq: 1,102 pkts [Networking] Dropped : 0 pkts 0.00% [Networking] OutOfOrder: 0 pkts 0.00% [Networking] Duplicate : 0 pkts 0.00% [Networking] SeqLurch : 0 pkts 0.00% [Networking] Ping histogram: (13 total samples) [Networking] 0-25 25-50 50-75 75-100 100-125 125-150 150-200 200-300 300+ [Networking] 4 4 0 2 0 0 1 1 1 [Networking] 30.8% 30.8% 0.0% 15.4% 0.0% 0.0% 7.7% 7.7% 7.7% [Networking] Ping distribution: [Networking] 50th 75th [Networking] 29ms 94ms [Networking] Connection quality histogram: (10 measurement intervals) [Networking] perfect 99+ 97-99 95-97 90-95 75-90 50-75 <50 dead [Networking] 9 0 0 0 0 0 0 0 1 [Networking] 90.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 0.0% 10.0% [Networking] Connection quality distribution: [Networking] 50th 25th [Networking] 100% 100% [Networking] Latency variance histogram: (1089 total measurements) [Networking] <1 1-2 2-5 5-10 10-20 >20 [Networking] 813 143 87 46 0 0 [Networking] 74.7% 13.1% 8.0% 4.2% 0.0% 0.0% [Networking] Backup router: sea#130 (205.196.6.212:27052) Ping = 86+4=90 (front+back=total) [Networking]
[NetSteamConn] Removing Steam Net Connection for =[A:1:2456525834:24179], handle #2541504226 [Client] CL: Server disconnected: 85: NETWORK_DISCONNECT_INTERNAL_ERROR [Client] CL: Disconnecting from server: NETWORK_DISCONNECT_INTERNAL_ERROR [Networking] Closing 'client' poll group [HostStateManager] CHostStateMgr::QueueNewRequest( Idle (levelload), 7 ) [HostStateManager] HostStateRequest::Start(HSR_IDLE): loop(levelload) id(7) addons() desc(Idle (levelload)) [EngineServiceManager] SwitchToLoop levelload requested: id [7] addons [] [Client] CL: IGameSystem::LoopDeactivateAllSystems { WriteSteamRemoteStorageFileAsync( "scripts/control_groups.txt" ) -> at 4276.964 [Host] HO: IGameSystem::LoopDeactivateAllSystems { [Host] HO: } IGameSystem::LoopDeactivateAllSystems done [Client] CL: } IGameSystem::LoopDeactivateAllSystems done [stringtables] CL: CNetworkStringTableContainer::RemoveAllTables: removing 19 tables LoadFullBodyLoadoutPortraitInfo failed to load scripts/npc/portraits_full_body_loadout.txt! [SteamNetSockets] [#2541504226 SDR server steamid:90175843018185738 vport 0] Discarding inactive session sea#130 (205.196.6.212:27052). ConnectionShutdown [SteamNetSockets] [#2541504226 SDR server steamid:90175843018185738 vport 0] Discarding inactive session atl#109 (162.254.199.178:27031). ConnectionShutdown ILocalize::AddFile() failed to load file "resource/localization/broadcastfacts_english.txt". [Client] CL: CGameRulesGameSystem::GameShutdown uninstalled game rules [Client] CL: CGameRules::CGameRules destructed WriteSteamRemoteStorageFileAsync( "voice_ban.dt" ) -> at 4277.577 ChangeGameUIState: DOTA_GAME_UI_DOTA_INGAME -> DOTA_GAME_UI_STATE_LOADING_SCREEN [Client] LoadingDisplay changed from NONE to LOADING (map="") [HostStateManager] Host activate: Idle (levelload) CAsyncWriteInProgress::OnComplete( "scripts/control_groups.txt" ) -> Success at 4277.599 CAsyncWriteInProgress::OnComplete( "voice_ban.dt" ) -> Success at 4277.599 [Client] CL: CLoopModeLevelLoad::MaybeSwitchToGameLoop switching to "game" loopmode with addons () [EngineServiceManager] SwitchToLoop game requested: id [7] addons [] [Server] CNetworkGameServerBase::SetServerState (ss_dead -> ss_waitingforgamesessionmanifest) [Server] SV: maxplayers set to 1 Initializing script VM... ...done [ResourceSystem] Failed loading resource "panorama/images/spellicons/dota_base_ability_png.vtex_c" (ERROR_FILEOPEN: File not found) [ResourceSystem] Failed loading resource "scripts/player.vdata_c" (ERROR_FILEOPEN: File not found) Panel TimeRangeSlider has fill-parent-flow for width, but isn't in a flowing right layout Panel TimeScrubSlider has fill-parent-flow for width, but isn't in a flowing right layout Panel SliderAndMarkers has fill-parent-flow for width, but isn't in a flowing right layout Panel TimeScrubSlider has fill-parent-flow for width, but isn't in a flowing right layout [Server] SV: Spawn Server: