Philipp Hancke

no reproduction so closing

Unlikely to happen in a reasonable timeframe

are you using any "privacy" extensions which might tamper with how WebRTC behaves? Not gathering any candidates is quite unusual

libwebrtc issue here: https://bugs.chromium.org/p/webrtc/issues/detail?id=13106, no movement for a while

Unlikely to happen in a reasonable timeframe

tagging @jan-ivar for triage

grabbing that data into `s` and then doing ``` majorVersions = {}; Object.keys(s.downloads).forEach(version => { const majorVersion = parseInt(version, 10); if (!majorVersions[majorVersion]) majorVersions[majorVersion] = 0; majorVersions[majorVersion] += s.downloads[version]; }); ```...

``` Object.keys(s.downloads).forEach(version => { const majorVersion = parseInt(version, 10); if (majorVersion < 6) return; console.log(version, s.downloads[version]); }) ``` at least mostly using the latest versions of 6 + 7

``` Object { 0: 14, 1: 3260, 2: 1958, 3: 4323, 4: 641, 5: 261, 6: 16590, 7: 119796, 8: 33792 } ``` Quite surprising 7.x is so popular given...

``` Object { 0: 18, 1: 5263, 2: 1952, 3: 7406, 4: 610, 5: 566, 6: 49052, 7: 146731, 8: 51352 } ``` https://npmtrends.com/webrtc-adapter shows quite a large bump recently