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
Disconnected nodes not closing properly. Leaving hung sessions #1564
Milestone
Comments
oops! |
Is that a good 'oops!' ?? :-) |
If you can attach visual studio to one of those and get a stack trace, that'd help see what's hanging. Not sure if there is a better or another way to get a stack trace on win32 |
Will do so next time I see the hung nodes. |
thanks! |
have you seen any since? Were you able to get a stacktrace? |
While I haven't done a trace, I actually recreated this multiple tomes over the last couple days while trying to get a Door to run.
Sent from my T-Mobile 5G Device
…-------- Original message --------
From: Rushfan ***@***.***>
Date: 5/12/23 4:27 PM (GMT-08:00)
To: wwivbbs/wwiv ***@***.***>
Cc: Jim ***@***.***>, Author ***@***.***>
Subject: Re: [wwivbbs/wwiv] Disconnected nodes not closing properly. Leaving hung sessions (Issue #1564)
have you seen any since? Were you able to get a stacktrace?
—
Reply to this email directly, view it on GitHub<#1564 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADFBHEPOKP5AU5QNV6YSOA3XF3B2LANCNFSM6AAAAAAUOMY46I>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#1564 (comment)", "url": "#1564 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows 10, w32. 5.8.0.3665
Increased instances of hung nodes.
I initially noticed this when under constant barrage on ssh port, now seeing on telnet ports but from known users.
The text was updated successfully, but these errors were encountered: