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

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Issue 673395: Implement RTCConfiguration.iceCandidatePoolSize

Reported by, Dec 12 2016 Project Member

Issue description

Comment 1 by, Mar 15 2017

Project Member
The following revision refers to this bug:

commit ff92bdcc0bed8878b0989f14993b3aec98a4769b
Author: deadbeef <>
Date: Wed Mar 15 05:06:18 2017

Add support for RTCConfiguration.iceCandidatePoolSize.

This is a performance optimization that will result in ICE candidates
being gathered before setLocalDescription has been called. Later, when
setLocalDescription *is* called, any pooled candidates will be fired
in an "icecandidate" event immediately.

Besides candidate gathering appearing to occur quicker, this optimization
doesn't have any effects visible to JavaScript.

Note that the pool size can only be changed before setLocalDescription,
as described by JSEP. This pool is only intended to be used for the
first offer/answer, after which an ICE restart must be used to gather
new candidates.

Intent to Implement and Ship thread:

BUG= chromium:673395 

Cr-Commit-Position: refs/heads/master@{#456998}


Comment 2 by, Mar 15 2017

Status: Fixed (was: Started)

Comment 3 by, Mar 27 2017

Labels: M-59

Comment 4 by, May 14 2018

Can you please let me know which version of webrtc contains this fix? doesn't specify which version this feature is available on.

Comment 5 by, May 15 2018

M-59 assuming the label is correct. Updated

Sign in to add a comment