IPFS: Thread handling crashes with webRTC and fails without it

[mitra42]

If you've downloaded any of the examples you'll see they crash after about 5 mins on Chrome before being killed by the browser, and slowly grind Firefox and your whole machine to a halt!

This is a IPFS bug, something to do with how its implemented webRTP and is reported at ipfs/js-ipfs#942 and Firefox - crashes with excessive thread activity

Several workarounds have been suggested, but until we can find someone who understands what was proposed and how to implement it it will remain broken.

[mitra42]

Note disabling WebRTP is one suggestion which does stop the crash, but means none of the examples involving lists will work.

[mitra42]

An update - still seeing this, all the examples are now setup to use HTTP to our content server as well as IPFS, and this is configurable.

there are now numerous topics relating to it since plenty of people seeing it. Here's the index:
ipfs/js-ipfs#950 - original post by me, closed (prematurely) as far from fixed.
ipfs/js-ipfs#1088 - posted by Beanow (since 950 was closed)
ipfs/js-ipfs#942 - same issue posted by Lightning in their app
ipfs-shipyard/shared-editing-demo#2 - in the Shared Editing demo
ipfs/js-ipfs#962 - Connection Closing - the potential solution
ipfs/js-ipfs#1089 - By Interfect - relating to crashing Firefox 57

[mitra42]

This is confirmed to be working with IPFSv0.27 though it switches to a single-point-of failure websockets transport. Hopefully fixes to webrtc will solve that problem.