fc47c86b12
Make the warning timeout for Event::Wait configurable, and let NullSocketServer::Wait pass kForever to completely eliminate the warning. 3000 ms is a good default warning timeout for Event::Wait, but in some cases---such as when a message queue is waiting for a message to arrive---we don't want the warning, since a long wait isn't a reliable indicator that the system is deadlocked. It might just be that no one is posting messages. Bug: webrtc:10531 Change-Id: Ic5969b8bfedb96376bd6d6a72ba6a4591750a920 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/132017 Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Commit-Queue: Karl Wiberg <kwiberg@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27574}
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