Assertion Failed: packet number not properly initialized!

[SDGNelson]

Several hosts have been reporting this assertion in standard output these past few days. Perhaps an issue introduced in the December 21st Steam client update?

Here is a full example from the log:

src\steamnetworkingsockets\clientlib\steamnetworkingsockets_connections.cpp (1935) : Assertion Failed: [#579068838 UDP steamid:76561198963144398@XXXX:51905] packet number not properly initialized!

[zpostfacto]

Thanks, I'll take a look. I've been trying to nail initialization of this packet number for a while. I am 99.9% sure the code heals this situation, so the assertion is harmless, but I'll take a look into it.

[ghost]

Hi @fletcherdvalve

Did you have by any chance some time to have a look at this issue? I am facing the exact same behavior with the Windows build of my application, Linux build works fine though. Both are using the GameNetworkingSockets built from tag v1.2.0.

[zpostfacto]

@synoga Do you have a reliable way to reproduce this?

[ghost]

I can try to extract some minimal example code from my project, I'll let you know If I can reproduce it this way :). I've tried to remove the assertion and the windows build could connect without issues, and the communication seems ok.

[zpostfacto]

Yes, it's been my expectation that the assertion is a noisy irritation but doesn't actually cause any problems, which is why I haven't been prioritizing this. If you can reliably reproduce it, or if it's actually causing connectivity issues, I'll bump this up.

[ghost]

While trying to reproduce, I rebuilt GNS on the server part of my application, and now I can't reproduce anymore, so I suspect I had some issue on that environment and that reminds me I should probably finish my CI ^^'

[TeemoCell]

Error still there /data/src/steamnetworkingsockets/clientlib/steamnetworkingsockets_connections.cpp (1935) : Assertion Failed: [#831113844 UDP steamid:[email protected]:30437] packet number not properly initialized! That message lags my server really bad.

[zpostfacto]

Is anyone still getting this? @SDGNelson @TeemoCell

[SDGNelson]

I'll ask around a bit

[SDGNelson]

It sounds like it is resolved! One host with 38 servers even ran a search on the past year of logs and didn't find any mention of this assertion.

[zpostfacto]

Great! No idea when it got fixed. Thanks for looking.