You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2019. It is now read-only.
Hi, I use the latest version in macOS 10.13, tokio-socks5 cpu usage is very high。
some log:
Listening for socks5 proxy connections on 127.0.0.1:8080
error for 127.0.0.1:58096: timeout during handshake
error for 127.0.0.1:58100: Connection reset by peer (os error 54)
error for 127.0.0.1:58101: Connection reset by peer (os error 54)
proxied 568/168 bytes for 127.0.0.1:58099
proxied 568/168 bytes for 127.0.0.1:58120
error for 127.0.0.1:58122: Socket is not connected (os error 57)
error for 127.0.0.1:58108: Connection reset by peer (os error 54)
error for 127.0.0.1:58127: timeout during handshake
error for 127.0.0.1:58128: timeout during handshake
error for 127.0.0.1:58134: timeout during handshake
connection may RST by firewall . use dtruss trace:
Hi, I use the latest version in macOS 10.13, tokio-socks5 cpu usage is very high。
some log:
connection may RST by firewall . use dtruss trace:
add some log in: https://github.com/tokio-rs/tokio-socks5/blob/master/src/main.rs#L557
and https://github.com/tokio-rs/tokio-core/blob/master/src/net/tcp.rs#L344
log output:
It looks like HUP, poll read and poll write both Ready but read returns WouldBlock.
some help?
The text was updated successfully, but these errors were encountered: