Initialize AVFoundation explicitly

chrome/browser/chrome_browser_main_mac.mm

Index: chrome/browser/chrome_browser_main_mac.mm
diff --git a/chrome/browser/chrome_browser_main_mac.mm b/chrome/browser/chrome_browser_main_mac.mm
index c097c49e4271d44132a9336d5f5202763231de42..25c17ad2a360233c49ca671b9b2def102ba3b81d 100644
--- a/chrome/browser/chrome_browser_main_mac.mm
+++ b/chrome/browser/chrome_browser_main_mac.mm
@@ -28,6 +28,7 @@
 #include "components/metrics/metrics_service.h"
 #include "content/public/common/main_function_params.h"
 #include "content/public/common/result_codes.h"
+#import "media/base/mac/avfoundation_glue.h"
 #include "ui/base/l10n/l10n_util_mac.h"
 #include "ui/base/resource/resource_bundle.h"
 #include "ui/base/resource/resource_handle.h"
@@ -121,6 +122,9 @@ void ChromeBrowserMainPartsMac::PreMainMessageLoopStart() {
   // The framework is only distributed with branded Google Chrome builds.
   [[KeystoneGlue defaultKeystoneGlue] registerWithKeystone];
 
+  // Initialize AVFoundation if supported, for audio and video.
+  AVFoundationGlue::InitializeAVFoundation();

[jam, 2015/05/26 23:13:47]

i think we want this in src/content so that all content-based browsers get it?

[tommi (sloooow) - chröme, 2015/05/27 09:11:02]

Yes, makes sense.  Put it in BrowserMainLoop::PreCreateThreads?

+
   // Disk image installation is sort of a first-run task, so it shares the
   // no first run switches.
   //