Re: Deadlock when trying to close a tab with disconnected server
I was not able to reproduce the problem. Can you please contact me?
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- martin
Re: Deadlock when trying to close a tab with disconnected server
Thanks for your report.
Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.
Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.
You will find my address (if you log in) in my forum profile.
- vicd
Deadlock when trying to close a tab with disconnected server
(Windows 10 22H2 19045.7291, WinSCP 6.5.6, SFTP)
WinSCP locks, waits for some period, then flashes a dialog about "Server not responding", but immediately closes it, and that just goes in cycles. No way to exit either then closing/terminating the process.
EXPECTED: if a server is disconnected AND the tab's Close button was pressed, don't attempt reconnecting. Just close the tab ignoring the connection state.
- New tab, connect to an SFTP server (some AWS Ubuntu in my case);
- Switch to some other windows, leaving WinSCP in background;
- Wait enough time for the server to drop/timeout the connection "due to no actions";
- Switch back to WinSCP and immediately click the [x] (Close) button of that tab.
WinSCP locks, waits for some period, then flashes a dialog about "Server not responding", but immediately closes it, and that just goes in cycles. No way to exit either then closing/terminating the process.
EXPECTED: if a server is disconnected AND the tab's Close button was pressed, don't attempt reconnecting. Just close the tab ignoring the connection state.