This message was deleted.
# announcementss
steep-balloon-41261
10/05/2022, 11:07 PMThis message was deleted.
d
dry-elephant-14928
10/05/2022, 11:25 PMare you able to reproduce this with either the react example or js example app?
dry-elephant-14928
10/05/2022, 11:25 PMif so, please share the steps and we'll take a look.
c
colossal-engine-37907
10/05/2022, 11:30 PMI can probably put one together
🙏 1
colossal-engine-37907
10/06/2022, 1:08 AMI've narrowed it down to a specific line of code that causes the problem. When a track is unsubscribed, we are calling track.mediaStreamTrack.stop(). This seems to put LiveKit in a bad state. If this line is removed, the track publications don't have an issue going back to the other side. Sample app that illustrates this issue
https://gist.github.com/jezell/208e9ec3d042ad9a44347fb95f892696
https://gist.github.com/jezell/e6fc211ce990ca229e6b233af5ec2e91
Maybe there is some kind of bug introduced when tracks are manually stopped during a TrackUnsubscribed event?
colossal-engine-37907
10/06/2022, 1:16 AMThis is likely the cause of a similar issue I had reported earlier (https://livekit-users.slack.com/archives/C01KZ61HZRR/p1663740429177429), since that code path would have also been activating this code which cleans up tracks when they are removed.
d
dry-elephant-14928
10/06/2022, 6:16 AMthank you for the detailed report. That is indeed the issue. LiveKit re-uses the transceivers in the peerconnection to avoid bloating the clients.
because of that, when you
stop👍 1
c
colossal-engine-37907
10/06/2022, 5:14 PMMaybe it could also provide some kind of error in the console when that happens or it could detect that it needs to not re-use the transceiver if the track has been stopped? We probably don't need to stop the mediaStreamTrack, but would have been a lot easier to track down the issue if at something had been written out to the console.
d
dry-elephant-14928
10/07/2022, 5:49 AMthat's a great idea.. we should log a warning here.
dry-elephant-14928
10/07/2022, 6:01 AMdry-elephant-14928
10/07/2022, 6:02 AMI think failing the subscription is the prudent thing to do here. We cannot control if the server reuses the transceiver or not. (the spec allows for it, and client stopping it locally doesn't give server any indication of it)
6 Views