| commit | 2072b87261a6505a88561bdeab3e7405d7038eaa | [log] [tgz] |
|---|---|---|
| author | Etienne Pierre-doray <etiennep@chromium.org> | Tue Mar 23 19:18:00 2021 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Mar 24 18:46:51 2021 |
| tree | 8e81cef2f739b265b4a9c587d02ef7a30080fc3b | |
| parent | e6e2f280ff2ba35f417b03286dc09fd3861e844b [diff] |
Reland "[Battery]: Delay start of TaskQueuePacedSender." Take 2 This is a reland of 89cb65ed663a9000b9f7c90a78039bd85731e9ae ... and f28aade91dcc2cb8f590dc1379ac7ab5c1981909 Reason for revert: crashes due to uninitialized pacing_bitrate_ crbug.com/1190547 Apparently pacer() is sometimes being used before EnsureStarted() Fix: Instead of delaying first call to SetPacingRates(), this CL no-ops MaybeProcessPackets() until EnsureStarted() is called for the first time. Original change's description: > [Battery]: Delay start of TaskQueuePacedSender. > > To avoid unnecessary repeating tasks, TaskQueuePacedSender is started > only upon RtpTransportControllerSend::EnsureStarted(). > > More specifically, the repeating task happens in > TaskQueuePacedSender::MaybeProcessPackets() every 500ms, using a self > task_queue_.PostDelayedTask(). > > Bug: chromium:1152887 > Change-Id: I72c96d2c4b491d5edb45a30b210b3797165cbf48 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/208560 > Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#33421} Bug: chromium:1152887 Change-Id: I9aba4882a64bbee7d97ace9059dea8a24c144f93 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/212880 Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#33554}
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.
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.