-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
socket fd leaks if dial timeout occur #37
Comments
Thanks for submitting this! I wont have time to dig in this week (PRs welcome!). I can try to dig in this weekend or the next, luck willing. |
I've been moving across the country and am super bogged down. I've not forgotten about this, but I don't know when I can get to it. PRs welcome! |
Can this still be reproduced? I experimented with dial timeouts on ubuntu today and couldn't reproduce leaked sockets. |
To my knowledge, all leaks were patched a while back.
…On Mon, Aug 10, 2020 at 8:50 AM Aleksandar Č. ***@***.***> wrote:
Can this still be reproduced? I experimented with dial timeouts on ubuntu
today and couldn't reproduce leaked sockets.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/sethgrid/pester/issues/37*issuecomment-671402203__;Iw!!NCc8flgU!LtYYAX1YaPlf0Ajm5QM6GAG0CoUtSitnhQDwSnO0XVy1gH-MZioVHAJ4Cs2MZBpsKA$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAHRU7FH5VT42X6RHDJUWMTSAACLFANCNFSM4FSD32OQ__;!!NCc8flgU!LtYYAX1YaPlf0Ajm5QM6GAG0CoUtSitnhQDwSnO0XVy1gH-MZioVHAJ4Cs2q1bXKJA$>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If dial timeout occur, opened socket fd will leak.
sudo lsof -n -a -p $(pidof processname) |grep "can't identify protocol" |wc -l
You will see many 'can't identify protocol' socket.
The text was updated successfully, but these errors were encountered: