Gamestate on long running server becoming null

Hey Epic,

I am observing that the client GameState (GetWorld()->GameState) is null when connecting to a dedicated server running for 2-3 days.

The server does not change maps as I am stress testing one long running game for issues like this.

I have logged the server and it seems that GameState is valid so it seems somewhere on the client calls to GetWorld()->GameState are returning null.

Does anyone at Epic have any suggestions on where to look for a possible cause of this issue? What might cause a GameState to stop replicating or become null on the client?

Best,
George
( www.playdaysofwar.com )

Hello Mentos,

I wouldn’t know a cause for this myself other than possible garbage collection problems but wouldn’t know where to begin. As this isn’t something that is easily reproducible, I’ll be asking around and I’ll let you know if I need any more information on the subject.

Unfortunately I haven’t been able to come up with much. I imagine they would be long, but would it be possible for you to upload the logs for a session where the GameState disappeared? It may be able to point to where the issue is occurring.

Hey , thanks for asking around. I don’t think the logs would be much help so I will continue to debug this on my end for now.

Hello Mentos,

This is only intended as temporary measure, but I converted your latest comment into an answer and I’m marking it as the accepted answer. This is only for tracking purposes so I know that this is currently a handled issue. If you do need any more help, please respond here and unaccept the answer. I’ll be happy to attempt to assist further.