da8a45fdaa
AllocationSequence uses legacy rtc::Thread message handling. In order to cancel callbacks it uses rtc::Thread::Clear() which uses locks and necessitates looping through all currently queued (unbounded) messages in the thread. In particular, these Clear calls are common during negotiation and the probability of having a lot of queued messages is high due to a long-running network thread function invoked on the network thread. Fix this by migrating AllocationSequence to task queues. Bug: webrtc:12840, webrtc:9702 Change-Id: I42bbdb59fb2c88b50e866326ba15134dcc6ce691 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/221369 Commit-Queue: Markus Handell <handellm@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34241}
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 here 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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs