SIGABORT: (signaling_thread_)->IsCurrent()

[José Luis Millán]

We are using libwebrtc in order to offer a C++ client for the mediasoup[1] ecosystem.

The latest working libwebrtc version was branch-heads/4606 (m94). While upgrading to branch-heads/6099 (m120) we're having the crash indicated in the email subject when calling `track->setEnabled()`, being 'track' an instance of `webrtc::MediaStreamTrackInterface`.

The call to `track->setEnabled()` is made through the app (or test) thread which does not need to be the signaling_thead provided to `webrtc::CreatePeerConnectionFactory`.

This was working on m94 and I wonder why now the track can only be handled by the signaling thread and whether there is a way to avoid it.

Any pointer is appreciated.

[1]: https://mediasoup.org/

--

José Luis Millán

[tudor....@gmail.com]

To anyone that can help with this: 

There's a bounty offered for fixing it: https://mediasoup.discourse.group/t/bounty-upgrade-libmediasoupclient/6075

[Tim Na]

Can you show where that (track->setEnabled()) is being called in your code? I wonder if it could be as simple as invoking PostTask with signaling_thread to avoid the issue. If it needs to be synchronous, you can use BlockingCall instead.

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/85ee3c9a-b080-46c0-9e17-f5aabe952a1dn%40googlegroups.com.

[tudor....@gmail.com]

Please have a look at the discussion on github: https://github.com/versatica/libmediasoupclient/pull/173