mumble-voip/grumble

[Bug] Maybe memory leak?

Opened this issue · 2 comments

mr-cn commented

We run a grumble server with Docker and we use it in a small load (max 4 players at a same time).

After 7 days usage, we found the server unavailable: you can connect to it but you can't speak in a channel, after a short of time it shows "No tcp ping response".

Then I checked the server:

  1. The log shows grumble received the clients' connections. But these fake connections won't disconnect.

  2. The memory usage is huge (1.9g)

  3. I captured the network and found it keeping sending me packets even after I quited the client.

It guess it caused by some resources not freed correctly.

Some screenshots:

Dup ACKs after clients quit

Huge memory usage

Mumble

Server log

(Clients will keep retrying, and you can see "new" clients increasing meanwhile no old connections closed)

actown commented

It's totally possible there's a memory leak somewhere. Have you or anyone else reproduced this yet? If so, exact steps to get into a high memory state would be handy. If you're comfortable creating a core if it happens again we can try taking a look at that to see what might be the cause, but I would much rather have steps to cause this.

mr-cn commented

After restarted it seems behaving normally..
If there's any new information, I will update.