mediasoup-client: Error Failed to execute 'createOffer' on 'RTCPeerConnection

Bug Report

Your environment

Operating system: Catalina 10.15.7
Browser version: chrome Version 87.0.4280.67 (Official Build) (x86_64)
mediasoup version: 3.6.16
mediasoup-client version: 3.6.12

Issue description

produce screen sharing with audio using getDisplayMedia.
close created producers.
produce screen sharing with audio again
then the error occurs and producing failed

Failed to produce DOMException: Failed to execute 'createOffer' on 'RTCPeerConnection': Session error code: ERROR_CONTENT. Session error description: Unknown transceiver.

This error occures only when selecting chrome tab with share video.

And It didn’t occur in chrome version 86.0.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 3
Comments: 31 (18 by maintainers)

Most upvoted comments

Ok, confirmed that:

This is a bug in libwebrtc/Chrome and not in mediasoup-client (even if easier to report everything to mediasoup project because we don’t request jsfiddles).
The issue does not happen in Chrome 88 or 89 (Canary).
According to the issue in libwebrtc they are gonna fix M87 soon.

So closing. Nothing to do in mediasoup-client side.

ibc on Nov 24, 2020

I don’t want to go to higher levels. The issue is clearly reproducible with my steps above and the error is in pc.setLocalDescription() (there may be more, but this is clear) so this is a regression in Chrome/libwebrtc.

I know that it’s easier to report issues here than in Chroimum/libwebrtc trackers since there they require a jsfiddle that reproduces the error and they don’t want to know anything about higher layers (such as mediasoup-client library). If I have time next week I’ll try to make a jsfiddle reproducing the bug by just using PeerConnections. If anyone can help on this, that would be great, but this is not a bug in mediasoup-client. I’ll keep this issue open for updates.

ibc on Nov 20, 2020

@ArmorDarks - I tried your workaround and it does avoid the error, but the offer size increases whenever you publish another stream. I worked around it by creating a new transport for each new track that is published.

andrewlin12 on Nov 21, 2020

Is this gone in Chrome 88/89? Then this was already fixed in https://bugs.chromium.org/p/chromium/issues/detail?id=1134686 but possibly not merged.

fippo on Nov 21, 2020

Right, I think no one is arguing with that, rather we are looking for what Chrome/libwebrtc doesn’t like about the way mediasoup-client uses browser APIs and maybe work around that while it is not fixed upstream.

BTW I have spent over an hour on reduced test case and wasn’t able to come up with one yet.

nazar-pc on Nov 21, 2020