New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 875213 link

Starred by 1 user
Status: Fixed
Owner:
█ jeroendb@chromium.org
Last visit 19 days ago
Closed: Aug 21
Cc:
█ emadomara@chromium.org
█ juberti@chromium.org
solenberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

stun/turns server missing from chrome://webrtc-internals

Reported by fi...@appear.in, Aug 17 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. open chrome://webrtc-internals
2. make a webrtc call, e.g. https://appr.tc/?debug=loopback
3. inspect webrtc-internals

What is the expected behavior?
it shows something along the lines of iceServers: [stun:64.233.165.127:19302, stun:[2A00:1450:4010:C08::7F]:19302, turn:64.233.161.127:19305?transport=udp, turn:[2A00:1450:4010:C08::7F]:19305?transport=udp, turn:64.233.161.127:19305?transport=tcp, turn:[2A00:1450:4010:C08::7F]:19305?transport=tcp]

What went wrong?
it shows iceServers: [, , , , ,] also in the json export. Note that the number of elements in the array seems to be correct.

Did this work before? Yes 69.0.3497.32

Does this work in other browsers? Yes

Chrome version: 70.0.3521.2   Channel: dev
OS Version: 
Flash Version:

Comment 1 by philipp....@googlemail.com, Aug 17

Components: -Blink>WebRTC Blink>WebRTC>Tools

Comment 2 by grunell@chromium.org, Aug 17

Labels: FoundIn-70 RegressedIn-70
Owner: deadbeef@chromium.org
Status: Assigned (was: Unconfirmed)
Taylor, can you have a look?

Comment 3 by grunell@chromium.org, Aug 17

Owner: juberti@chromium.org
Justin, can you please reassign this?

Comment 4 by juberti@chromium.org, Aug 17

Cc: emadomara@chromium.org
Owner: jeroendb@chromium.org

Comment 5 by juberti@chromium.org, Aug 17

Cc: juberti@chromium.org

Comment 6 by jeroendb@chromium.org, Aug 17 

Regression was introduced by https://chromium-review.googlesource.com/c/chromium/src/+/1161614.

Looking into what the right fix is.

Comment 8 by hbos@chromium.org, Aug 21

Status: Started (was: Assigned)

Comment 9 by hbos@chromium.org, Aug 21 

Thanks!

Comment 10 by jeroendb@chromium.org, Aug 21

Status: Fixed (was: Started)
Project Member

Comment 11 by bugdroid1@chromium.org, Aug 21 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1eeedddb954066956154bba9a0fbb5c7161cd035

commit 1eeedddb954066956154bba9a0fbb5c7161cd035
Author: Jeroen de Borst <jeroendb@chromium.org>
Date: Tue Aug 21 15:53:40 2018

IceServer's uri is no longer set, switching to using urls.

Bug:  875213 
Change-Id: Ida2e195ae818724a72012fb2f0907ef09adbde10
Reviewed-on: https://chromium-review.googlesource.com/1180366
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Hoi Pipeloi <jeroendb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584758}
[modify] https://crrev.com/1eeedddb954066956154bba9a0fbb5c7161cd035/content/renderer/media/webrtc/peer_connection_tracker.cc

Comment 12 by anatolid@chromium.org, Aug 27

Labels: M-70
►

Sign in to add a comment