Closed Rumatoid closed 1 year ago
Up! I Found the same issue. Connections are not closing.
Hello guys, thanks for reporting this issue. You have any minimal code to reproduce the problem? Thanks
Hello guys, thanks for reporting this issue. You have any minimal code to reproduce the problem? Thanks
Just use prepareRequestFunction and watch for TCP connections (in Linux for example)
I suppose that the reason is that timeout
event from the socket is not handled, so the connection wouldn't be closed, as in case of timeout it should be closed manually.
https://nodejs.org/api/net.html#event-timeout
PS: i guess that my issue couldn’t be the same as for the topic starter, but might be related as well. My issue is related to the active connections that are managed by the library growing despite actual connections with proxies closed and the browser that initiated the connection is closed as well, so the library doesn't recognize some cases of the closed connection.
Hello guys, thanks for your effort to report this issue. We have released version 2.2.1 that should not leak TCP connections anymore.
proxy-chain generate a lot of TCP connections without PC I have about 50 connections, but 150 with PC
Im using ProxyChain.Server with prepareRequestFunction