|
|
Created:
5 years, 1 month ago by honghaiz3 Modified:
5 years ago Reviewers:
pthatcher1 CC:
webrtc-reviews_webrtc.org, tterriberry_mozilla.com Base URL:
https://chromium.googlesource.com/external/webrtc@master Target Ref:
refs/pending/heads/master Project:
webrtc Visibility:
Public. |
DescriptionStop sending stun binding requests after certain amount of time.
Also stop it if the request timed out.
It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports.
BUG=
Committed: https://crrev.com/45b0efd378abef87676e6ec55516b10ce583ddac
Cr-Commit-Position: refs/heads/master@{#10899}
Patch Set 1 #
Total comments: 2
Patch Set 2 : #
Total comments: 8
Patch Set 3 : #
Total comments: 2
Patch Set 4 : #Messages
Total messages: 31 (16 generated)
Description was changed from ========== Disable the stun binding request for keeping stun alive. BUG= ========== to ========== Disable the stun binding request for keeping stun alive. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ==========
honghaiz@webrtc.org changed reviewers: + pthatcher@webrtc.org
https://codereview.webrtc.org/1465843004/diff/1/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/1/webrtc/p2p/base/stunport.cc#n... webrtc/p2p/base/stunport.cc:400: requests_.Send(new StunBindingRequest(this, false, stun_addr)); Can we change StunBindingRequest::keep_alive_ to StunBindingRequest::keep_alive_deadline_? It looks like it would be pretty easy, and then we could pass in something like 2 minutes here.
Patchset #2 (id:20001) has been deleted
Patchset #2 (id:40001) has been deleted
Patchset #2 (id:60001) has been deleted
Also removed re-starting the request if the stun-binding requests timed out as it has been retried for more than 50 seconds. https://codereview.webrtc.org/1465843004/diff/1/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/1/webrtc/p2p/base/stunport.cc#n... webrtc/p2p/base/stunport.cc:400: requests_.Send(new StunBindingRequest(this, false, stun_addr)); On 2015/12/02 22:38:08, pthatcher1 wrote: > Can we change StunBindingRequest::keep_alive_ to > StunBindingRequest::keep_alive_deadline_? It looks like it would be pretty > easy, and then we could pass in something like 2 minutes here. Done.
Description was changed from ========== Disable the stun binding request for keeping stun alive. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ========== to ========== Stop sending stun binding requests after certain amount of time. Also stop it if the request timed out. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ==========
https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:28: // Stop sending STUN binding request after this amount of time (in milliseconds) request => requests https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:30: const int KEEP_ALIVE_DEADLINE = 120 * 1000; 2 * 60 * 1000; // 2 minutes Might be more clear https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:68: if (rtc::TimeSince(port_->start_time()) <= keep_alive_deadline_) { I was thinking that "deadline" would be more an absolute time, not a relative time. In otherwords, "December 7th at 7pm PST", not "in 2 weeks". The latter is more like a "timeout" than a deadline". I was thinking more like this: if (now < keep_alive_deadline_) { // ... } That way the caller could specify deadline = now + timeout.
https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:249: // prepare STUN candidate. This comment is no longer true.
Patchset #3 (id:100001) has been deleted
Patchset #3 (id:120001) has been deleted
https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:28: // Stop sending STUN binding request after this amount of time (in milliseconds) On 2015/12/03 21:00:19, pthatcher1 wrote: > request => requests Done. https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:30: const int KEEP_ALIVE_DEADLINE = 120 * 1000; On 2015/12/03 21:00:19, pthatcher1 wrote: > 2 * 60 * 1000; // 2 minutes > > Might be more clear Done. https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:68: if (rtc::TimeSince(port_->start_time()) <= keep_alive_deadline_) { On 2015/12/03 21:00:19, pthatcher1 wrote: > I was thinking that "deadline" would be more an absolute time, not a relative > time. In otherwords, "December 7th at 7pm PST", not "in 2 weeks". The latter > is more like a "timeout" than a deadline". I was thinking more like this: > > if (now < keep_alive_deadline_) { > // ... > } > > > That way the caller could specify deadline = now + timeout. Done. https://codereview.webrtc.org/1465843004/diff/80001/webrtc/p2p/base/stunport.... webrtc/p2p/base/stunport.cc:249: // prepare STUN candidate. On 2015/12/03 21:00:57, pthatcher1 wrote: > This comment is no longer true. I don't understand. why?
lgtm https://codereview.webrtc.org/1465843004/diff/140001/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/140001/webrtc/p2p/base/stunport... webrtc/p2p/base/stunport.cc:351: // open during the call. Sorry, I meant this comment.
Thanks! https://codereview.webrtc.org/1465843004/diff/140001/webrtc/p2p/base/stunport.cc File webrtc/p2p/base/stunport.cc (right): https://codereview.webrtc.org/1465843004/diff/140001/webrtc/p2p/base/stunport... webrtc/p2p/base/stunport.cc:351: // open during the call. On 2015/12/03 22:45:53, pthatcher1 wrote: > Sorry, I meant this comment. Done.
The CQ bit was checked by honghaiz@webrtc.org
The patchset sent to the CQ was uploaded after l-g-t-m from pthatcher@webrtc.org Link to the patchset: https://codereview.webrtc.org/1465843004/#ps160001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1465843004/160001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1465843004/160001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_clang_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_compile_x64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_compile_x86_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios32_sim_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios64_sim_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_arm64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_asan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_msan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_tsan2 on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_asan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_compile_x64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) presubmit on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_drmemory_light on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by honghaiz@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1465843004/160001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1465843004/160001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_clang_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_compile_x64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_compile_x86_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios32_sim_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios64_sim_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_arm64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) ios_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_asan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_msan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) linux_tsan2 on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_asan on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_compile_x64_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) mac_x64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) presubmit on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_compile_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_drmemory_light on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_gn_dbg on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_gn_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL) win_x64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by honghaiz@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1465843004/160001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1465843004/160001
Message was sent while issue was closed.
Description was changed from ========== Stop sending stun binding requests after certain amount of time. Also stop it if the request timed out. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ========== to ========== Stop sending stun binding requests after certain amount of time. Also stop it if the request timed out. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ==========
Message was sent while issue was closed.
Committed patchset #4 (id:160001)
Message was sent while issue was closed.
Description was changed from ========== Stop sending stun binding requests after certain amount of time. Also stop it if the request timed out. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= ========== to ========== Stop sending stun binding requests after certain amount of time. Also stop it if the request timed out. It is going to be complicated to keep this and make it sync with the connection bind request as they may be on two different ports. BUG= Committed: https://crrev.com/45b0efd378abef87676e6ec55516b10ce583ddac Cr-Commit-Position: refs/heads/master@{#10899} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/45b0efd378abef87676e6ec55516b10ce583ddac Cr-Commit-Position: refs/heads/master@{#10899} |