One thing to note is that this is an issue in Google’s implementation of WebRTC. I wish the marketing gimmicks would stop and they would acknowledge outside eff

One thing to note is that this is an issue in Google’s implementation of WebRTC. I wish the marketing gimmicks would stop and they would acknowledge outside efforts. Stuff like this hurts the perception of WebRTC which is a shame. We are seeing more and more memory safe implementations of WebRTC. So I really think there is light at the end of the tunnel! * https://github.com/pion/webrtc https://github.com/pion/webrtc * https://github.com/shinyoshiaki/werift-webrtc https://github.com/shinyoshiaki/werift-webrtc Chromium itself sees constant CVEs so I don’t think this is a WebRTC specific issue. Documents like https://www.chromium.org/Home/chromium-security/memory-safety https://www.chromium.org/Home/chromium-security/memory-safet... give me hope.