Open avssav opened 3 years ago
Hello @avssav! :wave: we're sorry you found a bug... so first of all, thank you very much for reporting it.
To know about progress, check in Triage. All issues are considered Backlog Candidates until work priorities align and the issue is selected for development. It will then become part of our official Backlog.
I guess why memory can be eaten. When the kms falls, it starts to create a core dump and therefore begins to eat up memory. These are just my guesses.
Prerequisites
These are MANDATORY, otherwise the issue will be automatically closed.
Issue description
We use KMS 6.15.0 on AWS instance linux Ubuntu 18.04. It starts like:
Why is not KMS 6.16.0? I don't see any urgent updates in the version.
We get some crash of our server really rarely. It was at same time when KMS is eating unexpectedly much memory.
Next I attach glib error and backtrace of a crash.
How to reproduce?
I don't know
Expected & current behavior
(Optional) Possible solution
Info about your environment
About Kurento Media Server
About your Application Server
Run these commands
I run the command into docker container