mojo interface_registry.cc results in enormous stderr logs |
|||
Issue descriptionwhen running layout tests, we end up with an large amount of stderr output recorded from interface_registry.cc e.g. stuff like this: 03:50:23.626 1669 [15643:15643:0221/035023.369878:3460558570:WARNING:interface_registry.cc(217)] 03:50:23.626 1669 03:50:23.626 1669 InterfaceRegistry(navigation:frame): 03:50:23.626 1669 Owned by: 03:50:23.626 1669 content_browser@ run as: b64870f3-b095-4a32-a9dc-0486bcf519ed 03:50:23.626 1669 03:50:23.626 1669 Providing: 03:50:23.626 1669 capability: renderer containing interfaces: 03:50:23.626 1669 autofill::mojom::AutofillDriver 03:50:23.626 1669 autofill::mojom::PasswordManagerDriver 03:50:23.626 1669 blink::mojom::MediaSessionService 03:50:23.626 1669 blink::mojom::PermissionService 03:50:23.626 1669 blink::mojom::PresentationService 03:50:23.626 1669 blink::mojom::SensitiveInputVisibilityService 03:50:23.626 1669 blink::mojom::WebBluetoothService 03:50:23.626 1669 blink::mojom::WebSocket 03:50:23.626 1669 content::mojom::BrowserTarget 03:50:23.626 1669 device::mojom::GeolocationService 03:50:23.626 1669 device::mojom::SensorProvider 03:50:23.626 1669 device::mojom::VRService 03:50:23.626 1669 device::mojom::VibrationManager 03:50:23.627 1669 device::mojom::WakeLockService 03:50:23.627 1669 device::nfc::mojom::NFC 03:50:23.627 1669 device::usb::DeviceManager 03:50:23.627 1669 discardable_memory::mojom::DiscardableSharedMemoryManager 03:50:23.627 1669 media::mojom::InterfaceFactory 03:50:23.627 1669 media::mojom::RemoterFactory 03:50:23.627 1669 media::mojom::Renderer 03:50:23.627 1669 mojom::MediaDevicesDispatcherHost 03:50:23.627 1669 payments::mojom::PaymentRequest 03:50:23.627 1669 ui::mojom::Gpu 03:50:23.627 1669 03:50:23.627 1669 Requiring: 03:50:23.627 1669 From: content_renderer: 03:50:23.627 1669 browser 03:50:23.627 1669 03:50:23.627 1669 Bound to: 03:50:23.627 1669 content_renderer@3_1 run as: b64870f3-b095-4a32-a9dc-0486bcf519ed 03:50:23.627 1669 03:50:23.627 1669 Providing: 03:50:23.627 1669 capability: browser containing interfaces: 03:50:23.627 1669 blink::mojom::AppBannerController 03:50:23.627 1669 blink::mojom::EngagementClient 03:50:23.627 1669 blink::mojom::InstallationService 03:50:23.627 1669 content::mojom::ImageDownloader 03:50:23.627 1669 content::mojom::LayoutTestControl 03:50:23.627 1669 mojom::MediaDevicesListener 03:50:23.627 1669 03:50:23.627 1669 Requiring: 03:50:23.627 1669 From: content_browser: 03:50:23.627 1669 renderer 03:50:23.627 1669 03:50:23.627 1669 Binders registered for: 03:50:23.627 1669 * blink::mojom::MediaSessionService 03:50:23.628 1669 * blink::mojom::PermissionService 03:50:23.628 1669 * blink::mojom::PresentationService 03:50:23.628 1669 * blink::mojom::WebBluetoothService 03:50:23.628 1669 * blink::mojom::WebSocket 03:50:23.628 1669 * device::mojom::GeolocationService 03:50:23.628 1669 * device::mojom::VRService 03:50:23.628 1669 * device::mojom::VibrationManager 03:50:23.628 1669 * device::mojom::WakeLockService 03:50:23.628 1669 * media::mojom::InterfaceFactory 03:50:23.628 1669 * media::mojom::RemoterFactory 03:50:23.628 1669 * mojom::MediaDevicesDispatcherHost 03:50:23.628 1669 03:50:23.628 1669 * - denotes an interface exposed to remote per policy. 03:50:23.628 1669 03:50:23.628 1669 03:50:23.628 1669 these should all be DVLOG()s imo
,
Feb 22 2017
Sure, I can make them DVLOGs.
,
Feb 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3535e17ab8294f1b10b26eff05eb1fe2774b7391 commit 3535e17ab8294f1b10b26eff05eb1fe2774b7391 Author: rockot <rockot@chromium.org> Date: Wed Feb 22 19:34:20 2017 Service Manager: Reduce InterfaceProvider spec spam to DVLOG(1) Demotes this spam from LOG(WARNING) to DVLOG(1) because it's too noisy otherwise. BUG= 694939 Review-Url: https://codereview.chromium.org/2704303007 Cr-Commit-Position: refs/heads/master@{#452164} [modify] https://crrev.com/3535e17ab8294f1b10b26eff05eb1fe2774b7391/services/service_manager/public/cpp/lib/interface_registry.cc
,
Feb 22 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dpranke@chromium.org
, Feb 22 2017