Webtorrent-desktop: High CPU utilization

[izdi]

Version 0.3.3 (0-a5366c3) OS X El Capitan

Whats up with so high CPU utilization. Threads spawning during some period even after torrent's already downloaded.

After 5 minutes

[feross]

@izdi This is a known Chromium bug that will be fixed in 6-12 weeks.

See this issue: Creating then destroying connections causes 100% CPU https://bugs.chromium.org/p/webrtc/issues/detail?id=5733

[feross]

I made a build without WebTorrent trackers (so no WebRTC connections) and will try running it overnight and see how well it fares.

[feross]

The build that doesn't create WebRTC connections was still working fine for me come morning time.

[feross]

Chrome just released version 50. The fix we need is in version 51. Chrome waits 6 weeks between releases, and Electron updates the Chrome version after 2 weeks.

So we're looking at 8 weeks before this is fixed.

[feross]

As a stopgap solution for OS X only, we are going to disable WebRTC peers in the next version of WebTorrent (v0.4.0) since the 100% CPU issue is makes the app look broken, when it's not even our fault.

Once Chrome 51 is included in Electron, we'll undo this change and re-enable WebRTC peers on OS X.

PR here: https://github.com/feross/webtorrent-desktop/pull/511

[feross]

Electron 1.2.0 was just released, which includes Chrome 51. PR here: https://github.com/feross/webtorrent-desktop/pull/594