A brief dialogue from a YouTube video (Tsahi Levent-Levi) explaining why the Chrome chrome://webrtc-internals tab should be opened before starting a WebRTC session: the internals tab collects event history and statistics only while open, and opening it later will not recover past history. The speakers note that Chrome previously collected data even when the tab was closed, but that caused memory leaks so the behavior changed.
Chapters
Why do we open Chrome WebRTC internals tab before starting WebRTC session?
What we commonly see is that when we ask for a worker internals dump, people are like, oh, let me open Chrome Webber internals and then send you the dump of the session. But if I need to look at such a dump, it's like, I know the current state of the connection, but I don't know how it got there. And in order to understand the bug, you need to see how it evolves over time, what happened at what point in time, and then see the complete story.
So WebRTC Internals doesn't, or let's say this Chrome does not collect the events and the statistics that we're looking for unless the WebRTC Internals tab is open beforehand. And if it's not open and we open it later, we won't have all of that history that is important for us when troubleshooting.
Correct. It used to do that like eight, nine years ago, but that turned out to be a memory leak because, oh, you collect a lot of data and then you never release it. Not a good idea.
And you almost never use it.
Exactly. So for all the people that were using a video conferencing application, never opened Chrome WordPress internals, it still created this memory pressure.
