Those errors are from ipfs, I don't think they're related.
It does not always get stuck in this loop.
The reload is being called by the endOfStream(PingStream, triggerReload) line.
The PingStream is timing out, so we need a more tolerant way of handling a ping timeout than reloading.
The change we made to "fix" this was based on a misunderstanding -- I'm reverting that change now which may cause this issue to re-appear. See https://github.com/MetaMask/metamask-plugin/issues/873 for more info
fyi ^ @ChicoBitcoinJoe
@ropod7
I will take another look at this
We are calculating extension comms failure with a setTimeout -- messages seemed to be blocked, and then the timeout triggers the redirect.
I think we could use a series of smaller setTimeouts to calculate an unblocked time span
It's fixed. Thanks!
Most helpful comment
@ropod7
I will take another look at this