C++ exception causing GWSockets to fail after server uptime of ~9 days

[Bagellll]

After about 9 days of uptime using GWSockets, my x86-64 server can no longer create websockets. So far, this has happened twice and does not fix until after a restart.

Only error reported is: [ERROR] C++ exception

[FredyH]

Do you know if it might be a problem of it running out of memory? Could you maybe check the memory shortly before it crashes?

[Bagellll]

The server doesn't crash, it seems that only GWSockets stops working. It's also hard to get much info from it since it takes over a week to happen. As far as memory goes, it stays around ~2GB and slowly creeps up. Though, I don't think memory wouldn't be an issue unless you have a local arena because the server is running x64. I forgot to mention I'm using Linux also.

[FredyH]

I think I've also encountered this with another module of mine if the memory hits ~2.1GB, at which it starts not being able to allocate memory anymore. I don't believe it is due to a memory leak but just that it is not allowed to allocate RAM past that point, I will have to look into it.

[Bagellll]

It's just very strange to me. Now that I think about it, I also use the reqwest module and both stop working. The server continues fine until I've manually restarted it, with RAM usage continuing to go up well past 2GB if I leave it. I also have your MySQLOO module installed and it continues to work just fine.

[FredyH]

I found one case where a memory leak on the GWSocket side is possible. I fixed it in the latest Beta release, feel free to try it out.