1879844 - WebRTC ICE candidate selection takes more than 30 seconds

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Networking, defect)

Description

[hasan]

Attachment: firefox-issue.pdf

Steps to reproduce:

I have a web application that uses webrtc for media streaming. I'm forcing it to use a relay (CoTurn) as the other endpoint may or may not have a public ip. It works without a problem with any chromium based browser (chrome, opera, edge etc.) but ICE selection takes a very long time in Firefox. I can privately share a link to it if needed for debugging. I'm attaching all relevant info in a single file as I'm not sure how to add multiple files.

Actual results:

The ICE candidates are enumerated very quickly. I see some .local candidates but they fail quickly. But the successful candidates hangs for about 30 seconds before one is selected.

Expected results:

Once all the ICE candidates are either succeded or failed it should immediately select one and continue to establish a Peer Connection.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:bwc, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Byron Campen [:bwc]]

It looks like Firefox is the answerer in the scenario in the attached file. By default, the offerer is the ICE controller (the side that is responsible for nominating ICE candidates), so we're probably waiting on the other side to nominate here. I could know for sure if I had a packet capture.