New issue
Advanced search Search tips

Issue 717772 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Add WebRTC log messages to help narrow down common video capture issues

Project Member Reported by chfremer@chromium.org, May 2 2017

Issue description

Add additional log messages to the video capture stack strategically to allow narrowing down issues like the following:
* Video frames do not arrive at WebRTC encoder output
* Webcam is not found
* Webcam does not deliver any frames
 

Comment 2 by guidou@chromium.org, May 25 2017

Status: Assigned (was: Untriaged)
Changing status to assigned since this bug has ann owner.
Status: Started (was: Assigned)
Update on this: I had left this issue open, because I was planning to land a second CL with more logging. After preparing the CL [1], I realized that the extra logs, would not actually make it to the WebRTC logs, because the log uploader is not connected as a listener until an actual call session is started.

As a potential approach around this I considered storing the logs temporarily in memory until a call is started, but that does not seem like a good solution, because it would accumulate logs indefinitely even in cases where a Hangouts/Meets call is never started.

A slightly less bad apporoach would be to collect a limited amount of logs in a circular buffer, but that still seems super wasteful for cases where a Hangouts/Meets call is never started.

Any ideas on this? If I can't find a good solution, I will close this issue and abandond the CL [1].

[1] https://chromium-review.googlesource.com/c/chromium/src/+/644570

Sign in to add a comment