You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have built a stand alone server that sends out a heartbeat every 5 seconds.
My Unity client connects to the server via websocket and displays the heartbeat message it receives. After 3 hours, Unity will freeze and lock up and I have to use task manager to kill it. I can repeat this 100%. Using Unity 6000.0.35f1
I have the same client program running in Godot via WebSocketPeer and it runs with no problem so it's not the server.
Does the NativeWebSocket require some type of "reply" from the client to maybe keep the connection alive?