Add WebRTC log messages to help narrow down common video capture issues |
|||
Issue descriptionAdd 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
,
May 25 2017
Changing status to assigned since this bug has ann owner.
,
Dec 7 2017
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 |
|||
Comment 1 by bugdroid1@chromium.org
, May 4 2017