We found this native WebRTC log from a video meeting started with:

[000:022] Codecs supported by the external encoder factory: H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264

Well that's not very useful. What's worse was this gets logged repeatedly / frequently. And by the end of the video meeting it had become this:

[1863:182] Codecs supported by the external encoder factory: H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264, H264

So why did it grow? This seemed to be a single-participant test meeting.

Is there anything else unnecessarily logged in these logs?
 

Deleted: 92110f89c0000000.log 3.9 MB

92110f89c0000000.log 3.9 MB View Download