tor freeze when receiving to many http proxy requests on socks port
After receiving 724
curl 127.0.0.1:9150 (number was very consistent for me, but maybe somehow platform dependent?), tor stop doing anything. I can't reproduce that issue with a
tor not started by TB. Arma intuition is it could be TB isn't reading tor logs "fast enough" so tor end up blocked on trying to write to its stdout.
Note: these requests are invalid by tor standards: tor does not accept http requests on its socks port, and answer them with a basic "this is not how to use tor" webpage (and logs a complain).
Log warn stdout causes the error to appear after 740 curls, and
Log err stdout make it never is an issue, so it is indeed an issue of not reading tor stdout fast enough (or at all possibly?), and getting blocked when the pipe is full.