-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Worker dies as soon as client transport connects #580
Comments
@vpalmisano may you please take a look? It seems related to the changes in |
@euthyphro666 can you try with mediasoup version 3.7.1? My modifications are present starting from version 3.7.2. |
Looking at it. The crash is in this line: https://github.com/versatica/mediasoup/blob/v3/worker/src/RTC/PipeConsumer.cpp#L206 There is no entry in the |
@euthyphro666, Please enable the 'rtp' worker debug tag and set the worker 'debug' level so you can provide us with the worker logs too. https://mediasoup.org/documentation/v3/mediasoup/debugging/ Also, if you could try several diffent mediasoup tags between 3.5.12 to 3.7.11 that will narrow the culprit too. |
Thank you guys for the quick replies and suggestions. I tested against a few versions as suggested with no success until I tested with the previous version of the client I had been using and it worked with 3.7.11. That's when I found the issue. My production environment requires the project to be bundled up with pkg. This requires that I copy the mediasoup-worker binaries into the payload. Apparently, that process was failing silently so despite upgrading to mediasoup version 3.7.11 I was still using mediasoup worker binaries compiled against 3.5.12. I'm so sorry for wasting all of your time. Once again, thank you for the quick responses and helpful insights. You all are awesome! |
Thanks a lot for the update @euthyphro666 ! |
Issue description
Similar to issue #537. Unlike that issue, the transport connection parameters has a populated fingerprint list. The software worked fine and would stream properly, however, right after upgrading mediasoup from 3.5.12 to 3.7.11 this issue started occurring.
As soon as any client connects its transport to the server, the transport immediately changes its state to disconnected and a mediasoup worker dies. The attached image hopefuly will show the timeline of events a little more clearly.
Your environment
Core Dump
The text was updated successfully, but these errors were encountered: