25eeda1872
When epoll is enabled in the PhysicalSocketServer, a socket may not get registered for its epoll events. If an AsyncSocket is closed and re-created during one of its signal callbacks, its old epoll events and new epolls events bitmasks may be the same, even though the fd has changed. This causes the epoll implementation to not register the new fd for any events. Fix this by resetting the saved events bitmask when the socket is closed. This ensures the new fd, if any, is registered if needed. Bug: webrtc:11497 Change-Id: Idea499e09aefdf292430d1a774a046f963603b95 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/173103 Reviewed-by: Taylor <deadbeef@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Commit-Queue: Karl Wiberg <kwiberg@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31039}
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct