commit | 979c268830794316dc1d05ea7242eb7310f6bc23 | [log] [tgz] |
---|---|---|
author | skvlad <skvlad@webrtc.org> | Fri Jun 10 22:24:13 2016 |
committer | Commit bot <commit-bot@chromium.org> | Fri Jun 10 22:26:24 2016 |
tree | b36434ab79f1708bac6ead1e20f28f0dc76bc794 | |
parent | 5d97a9a05b928ac50e14a0e4d8aaa42298cad056 [diff] |
Do not reconnect the network change signal each time the network manager is started Due to a bug, the NetworkManager was reconnecting to the NetworkMonitor's NetworkChanged signal every time the network manager is stopped and restarted. After each calls, one more listener was added to the signal and never removed - which caused OnNetworksChanged to be called multiple times on each actual network change. Not sure if this had any negative effect other than the extraneous "Network changed" lines in WebRTC logs, but it wasn't working correctly either way. The fix is to only subscribe to the signal once, when the NetworkMonitor is created. TBR=pthatcher BUG= NOTRY=True Review-Url: https://codereview.webrtc.org/2054583002 Cr-Commit-Position: refs/heads/master@{#13105}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.