Closed
Bug 1334682
Opened 9 years ago
Closed 9 years ago
Start trickle grace timeout only when remote candidates are available
Categories
(Core :: WebRTC: Networking, defect, P2)
Core
WebRTC: Networking
Tracking
()
RESOLVED
FIXED
mozilla54
| Tracking | Status | |
|---|---|---|
| firefox54 | --- | fixed |
| backlog | webrtc/webaudio+ |
People
(Reporter: drno, Assigned: drno)
Details
Attachments
(1 file)
Currently we start the trickle candidate timer as soon as offer answer concludes. That means we fire ICE failure if the remote side is not fast enough in providing its candidates.
But as long as we don't have any remote candidates there is nothing to check. So lets start this timer only when we really have received remote candidates.
BTW: should not start this timer if the SDP contained already the end-of-candidate indicator (e.g. from non-trickle implementations)?
BTW2: should we cancel this timer when we receive the end-of-candidate via trickle?
| Assignee | ||
Updated•9 years ago
|
backlog: --- → webrtc/webaudio+
Rank: 25
| Comment hidden (mozreview-request) |
Comment 2•9 years ago
|
||
| mozreview-review | ||
Comment on attachment 8831330 [details]
Bug 1334682: start trickle timeout only after we have received at least on candidate.
https://reviewboard.mozilla.org/r/107890/#review109098
It looks like we will not start this timer if we get a remote trickle candidate, then offer/answer completes (and we start ICE), and then we discover our first local candidate. I guess this could happen if we're operating in no_host mode?
Attachment #8831330 -
Flags: review?(docfaraday)
| Assignee | ||
Updated•9 years ago
|
Summary: Start trickle timeout only when remote candidates are available → Start trickle grace timeout only when remote candidates are available
| Comment hidden (mozreview-request) |
Comment 4•9 years ago
|
||
| mozreview-review | ||
Comment on attachment 8831330 [details]
Bug 1334682: start trickle timeout only after we have received at least on candidate.
https://reviewboard.mozilla.org/r/107890/#review109334
::: media/mtransport/third_party/nICEr/src/ice/ice_peer_ctx.c:439
(Diff revisions 1 - 2)
> ABORT(r);
>
> if ((r = nr_ice_media_stream_pair_new_trickle_candidate(pctx, pstream, cand)))
> ABORT(r);
>
> + /* Start the remote trickle grace timeout if it hasn't been started by
Remove "by"
Attachment #8831330 -
Flags: review?(docfaraday) → review+
| Comment hidden (mozreview-request) |
Pushed by drno@ohlmeier.org:
https://hg.mozilla.org/integration/autoland/rev/cee7ea05a851
start trickle timeout only after we have received at least on candidate. r=bwc
Comment 7•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in
before you can comment on or make changes to this bug.
Description
•