We at WebinarGeek, like many web apps, rely heavily on the stability and performance of Google Chrome. Chrome is the dominant browser in our user base and powers our media streaming solution that is build upon WebRTC.
So, we rely on Google Chrome and it is important that things keep working. But what if they don’t? And what if it only happens for a small percentage of your users? And what if you can’t reproduce it? You need some help, some tooling, a lot of time and some luck, but we figured it out.
The issue
Part of our web app relies on functionality within WebRTC that allows a MediaStream to be relayed to another peer. I have a video meeting with person X, and then I relay the video of person X to person Y. …
