diff options
| author | mcasas@chromium.org <mcasas@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-12 09:27:25 +0000 |
|---|---|---|
| committer | mcasas@chromium.org <mcasas@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-12 09:27:25 +0000 |
| commit | 08f2c54c587f87d11520bdf4bd1dd3c5475c02e0 (patch) | |
| tree | 7b46ce372e7f05d2ba0653ffc14217dab5901428 /courgette/disassembler_elf_32_arm.h | |
| parent | d36b82b29d8f80c022bc8a800e5252d828bcfc0b (diff) | |
| download | chromium_src-08f2c54c587f87d11520bdf4bd1dd3c5475c02e0.zip chromium_src-08f2c54c587f87d11520bdf4bd1dd3c5475c02e0.tar.gz chromium_src-08f2c54c587f87d11520bdf4bd1dd3c5475c02e0.tar.bz2 | |
Mac AVFoundation/QTKit: delay DeviceMonitorMac startup to first GetUserMedia.
Currently DeviceMonitorMac is constructed from BrowserMainLoop in the
first compasses of Chrome bringup. DeviceMonitorMac creates either a
QTKitMonitorImpl or a AVFoundationMonitorImpl, that immediately
starts observing the system capture devices. This monitoring is
not needed until the user actively starts operating the devices,
that happens in MediaStreamManager.
This CL adds a method StartMonitoring() to DeviceMonitorMac that is
exercised from MediaStreamManager::StartMonitoring().
The performance regression in bugs 349616 and 348020 affects only
AVFoundation, but both implementations would benefit from a delayed
startup.
Tested locally via using --[enable/disable]-avfoundation, connecting
and disconnecting devices etc.
BUG=288562, 349616, 348020
Review URL: https://codereview.chromium.org/189443010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@256483 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'courgette/disassembler_elf_32_arm.h')
0 files changed, 0 insertions, 0 deletions