I have a weird problem where webrtc ice gathering is not working in a certain Chrome profile, and as a result the connection is stuck "new" and "not connected".
Take for example the trickle ice example from the official samples: (
https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/), this example works in all profiles except my main profile.
After clicking "Gather candidates" the list of candidates stays empty and webrtc-internals look like this:
ICE connection state: new
Connection state: new => closed
Signaling state: new => have-local-offer
ICE Candidate pair: (not connected)
Time Event
05/03/2024, 08:47:17 createOffer
05/03/2024, 08:47:17 createOfferOnSuccess (type: "offer", 2 sections)
05/03/2024, 08:47:17 setLocalDescription (type: "offer", 2 sections)
05/03/2024, 08:47:17 setLocalDescriptionOnSuccess
05/03/2024, 08:47:17 signalingstatechange
05/03/2024, 08:47:17 transceiverModified [0], audio
05/03/2024, 08:47:17 icegatheringstatechange
05/03/2024, 08:47:17 icegatheringstatechange
05/03/2024, 08:47:17 close
05/03/2024, 08:47:17 connectionstatechange
Looking at Wireshark I can confirm that Chrome never sends a request to the TURN server.
Has anyone seen this before?