Use the mediasoup Discourse Group for questions and doubts regarding mediasoup and its ecosystem.
You can also check for historical discussions in the mediasoup Google Group (previously used as mediasoup support forum).
mediasoup is an Open Source project supported on a best effort basis. Before asking any questions, please check the documentation and the F.A.Q. (the response may be there).
Please do NOT open an issue in GitHub for questions or doubts. Use the mediasoup Discourse Group instead.
If you get a crash in mediasoup server, this is, if you get an error log as follows:
2020-01-06T16:02:57.965Z mediasoup:ERROR:Worker worker process died unexpectedly [pid:22, code:null, signal:SIGABRT]
or if the worker.on(“died”) event fires, this is a bug in mediasoup that should not happen.
If so, please report the issue in GitHub and also enable core dumps in your host.
If you run mediasoup in Linux, do the following before running your mediasoup application again:
$ mkdir /tmp/cores $ chmod 777 /tmp/cores $ echo "/tmp/cores/core.%e.sig%s.%p" > /proc/sys/kernel/core_pattern $ ulimit -c unlimited
Then run your mediasoup application. If the crash happens again you should get a core dump in the
/tmp/cores folder. Open it with
gdb and attach it into the issue reported in GitHub:
$ gdb PATH_TO_YOUR_NODE_APP/node_modules/mediasoup/worker/out/Release/mediasoup-worker PATH_TO_COREFILE
Then, within the
gdb> bt full
Crashing processes in OSX automatically got a crash report in
You can check whether your setup works by manually generating one as follows:
$ pidof mediasoup-worker 46717 46718 46719 46720 $ kill -s SIGSEGV 46717
Then check the generated core dump or crash report file in the corresponding folder.