Ignoring Signal SIGPIPE will fix this crash
This usually happens when you write to a socket already closed on the other end (client) side
The client program (browser using the SOCKS) doesn't wait till all the data from the server is received and simply closes the socket which crashes controller if SIGPIPE is not handled.
Ignoring Signal SIGPIPE will fix this crash This usually happens when you write to a socket already closed on the other end (client) side The client program (browser using the SOCKS) doesn't wait till all the data from the server is received and simply closes the socket which crashes controller if SIGPIPE is not handled.