-
Notifications
You must be signed in to change notification settings - Fork 10
Kurento 6.15.0 crushes #599
Comments
Hello @avssav! 👋 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. |
Our another kurento was crashed yesterday. Dump file didn't create but I have some logs. Maybe it will helps
|
One more crush on low load service (
|
An another one:
|
@avssav are you using DataChannel? |
@j1elo Where can I see to use of the method? We connect to the kurento server through our node.js kurento-client. It was forked and rewritten from https://github.com/Kurento/kurento-tutorial-node/tree/master/kurento-one2one-call with using socket.io and ws npm modules and kurento-client-js and kurento-utils-js a few years ago. After that I update npm modules in our package.json, kurento-client-js and kurento-utils-js, Because they were changing from one version of kurento to another. We are now using the standard docker kms image 6.15.0 (there are plans to upgrade to 6.16.0 now because kurento-client-js and kurento-utils-js have some upgrades) |
It doesn't look that you are using DataChannels in https://github.com/avssav/novakid-kurento-client So the fact that Kurento stack trace points to some DataChannel methods, could indicate a memory corruption bug, that ends up with a crash. Are you able to identify if the crash happens with some scenario? Like:
So I can try to replicate your conditions with the kurento-one2one-call, to see if I can also get the same crash which would help me investigate the issue. |
There a lot of one2one pair of clients connected (10-70 pair). Different geographic areas. Load doesn't matter. This does not happen often |
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 crush of our server really rarely.
Next I attach backtrace of a crash.
I see some malloc problems in backtrace. But I don't see any memory problems on the AWS instance.
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
The text was updated successfully, but these errors were encountered: