53400 Error every time Mac computer goes to sleep

[sarahtully]

• I have verified that the issue occurs with the latest twilio-video.js release and is not marked as a known issue in the CHANGELOG.md.
• I reviewed the Common Issues and open GitHub issues and verified that this report represents a potentially new issue.
• I verified that the Quickstart application works in my environment.
• I am not sharing any Personally Identifiable Information (PII)
  or sensitive account information (API keys, credentials, etc.) when reporting this issue.

Code to reproduce the issue:
This issue was reported in the past but it appeared to be related to peer to peer or web SDK + iOS SDK usage. So I am opening a new issue.

1. Connect to a Twilio group room
2. Turn on camera and mic
3. On a Mac, go to Apple > Sleep
4. Once the monitor goes to sleep, move the mouse to bring back the display

Expected behavior:

1. Local user reconnects to the room and can see remote AV with no errors or memory leaks.

Actual behavior:

1. Local user reconnects to the room, but remote video is black and no longer receiving bytes. If the remote user un-publishes and republishes their media, we get the same errors along with periodic memory leaks.
2. Upon disconnecting from the same room, we receive a 53400 error every single time: TwilioError: Client is unable to create or apply a local media description.
3. Room SID: RM0ea81fcd929978467a95016dcb18a203

When performing this test with only a local user and no remote participants the same results occur. Room SIDs: RM7a4b77c6b3c19fe19984a0ee75289622 and RMde2cdbc908c0d43c2fe6fda599373461

Software versions:

• Browser(s): Chrome 94.0.4606.81
• Operating System: Mac OS Big Sur 11.6.1
• twilio-video.js: 2.17.1
• Third-party libraries (e.g., Angular, React, etc.): Angular 10.2.3

[PikaJoyce]

Hi @sarahtully!

Thank you for submitting this issue. I do see similar ICE Failures on my end as well. I appreciate the useful information you've provided and we're currently looking into this and I'll also file an internal ticket to track this issue. In the meantime, I'll keep this thread updated.

Thanks!
Joyce

[PikaJoyce]

Hey @sarahtully,

Small update, but I've been able to reproduce this consistently and the ticket that I've filed to track this issue is VIDEO-7426. Thank you for your patience!

Best,
Joyce

[sarahtully]

Thank you, Joyce, for your quick response.

[charliesantos]

This is a webrtc issue on chrome https://bugs.chromium.org/p/chromium/issues/detail?id=1263548
We'll see if we can find a workaround while waiting for a fix.

[makarandp0]

@charliesantos @sarahtully can you see if the workaround mentioned in #1447 help for this case?

[sarahtully]

@charliesantos thank you, we will try the workaround and get back to you.

[sarahtully]

@charliesantos At first I thought the workaround worked but I realized localhost was causing my window to livereload upon coming back each time. After deploying the suggested workaround to the server though it doesn't appear to fix the issue. I no longer receive the 53400 media description error, but it appears as though the Twilio room is consistently hung in a "reconnecting" state and we never successfully reconnect.

const pc = room?._signaling?._peerConnectionManager?._peerConnections.values()?.next()
      ?.value?._peerConnection;
if (pc) {
    pc.addEventListener('signalingstatechange', async () => {
        if (pc.signalingState === 'closed') {
          room.disconnect();
        }
    });
}

[charliesantos]

Hi @sarahtully , thank you for trying the suggested workaround and sorry if it didn't work in your case. We need chrome to address this bug on their side. https://bugs.chromium.org/p/chromium/issues/detail?id=1263548
Fortunately, they already acknowledge the issue.

[charliesantos]

Chrome issues related to this
https://bugs.chromium.org/p/chromium/issues/detail?id=1083204
https://bugs.chromium.org/p/chromium/issues/detail?id=1060547