Steven Allen

> Yup :) See my reply above for the manual part. As for leaving artifacts files after IPFS crashes.. I don't know how to properly resolve that. The real fix...

We should implement a *max* connections but high/low water are really designed to be target bounds. The libp2p team is currently refactoring the "dialer" system in a way that'll make...

Note: there's actually another issue here. I'm not sure if limiting the max number of *open* connections will really fix this problem. I haven't tested this but I'm *guessing* that...

We actually do that (mostly to avoid running out of file descriptors). We limit ourselves to opening at most 160 TCP connections at the same time.

We've been doing it for quite a while however, we may have changed some constants. I'm not sure.

In general, browsers assume that security origins are insensitive. With `ipfs://hash`, `hash` is the security origin.

> I tried following the steps here: https://github.com/ipfs/go-ipfs/blob/master/docs/debug-guide.md Ah, sorry, those are the instructions for the latest master (next release). Here are the instructions for v0.9.1: https://github.com/ipfs/go-ipfs/blob/v0.9.1/docs/debug-guide.md, the script is...

> All of the following hang. _That_ is bizarre. I've seen this kind of thing before, but it usually means IPFS is out of memory (which doesn't look like the...

> I checked and there was no dmesg output from that time. Is there any particular reason you are interested in dmesg? Seems like an odd place to look for...

> Nothing. Also this system is almost always lightly loaded on RAM > Although IIUC go-ipfs is just one process so if it was OOM killed it shouldn't hang, just...