Atem Serem
Atem Serem
@Kiessar Indeed, that could be an explanation but that would mean that the server is closing the connection before sending you the error. And yes, it would be a good...
@Kiessar I pushed a new release with support of timeout and sleep_time. Please let me know if it can help.
@Kiessar No problem. :)
@Kiessar Any news ?
@Kiessar Ok good, please let me know your findings.
I pushed a new version with an updated version of websockets. Maybe it will help.
@Kiessar Ok thanks, I will try to reproduce it as well and see if something can be done at the client's side.
@Kiessar I tried to run a simple implementation and my script got killed by the OOM killer. Did you also got an increase of memory over time ?
Good to know but in that case, it's just simply listening the websocket and printing the output.
@Kiessar For the memory error, yes it's probably that. If I understand well, you are opening 5 websockets connections, right ? And 4 of them did not reconnected ?