lrio wrote:

Does this mean bug 757 is also fully resolved in 5.12? Or is that issue different in a way I'm not seeing?

I do not see any relation.
Though Bug 757 is actually implemented by Bug 1564:
https://winscp.net/tracker/1564
I've just forgot to close the 757 itself.

martin wrote:

As you can see in the tracker link above, this will be resolved in upcoming WinSCP 5.12.

Does this mean bug 757 is also fully resolved in 5.12? Or is that issue different in a way I'm not seeing?

5.12 beta has been released meanwhile.

As you can see in the tracker link above, this will be resolved in upcoming WinSCP 5.12.

I saw your post about resolving in v5.12 after my post. Anyway, it will be great improvement :)

Thanks for resolving!

radojko wrote:

The same situation here, it is very frustrating to wait so long time when you cancel a job.
This problem exist i think from always.

As you can see in the tracker link above, this will be resolved in upcoming WinSCP 5.12.

The same situation here, it is very frustrating to wait so long time when you cancel a job.
This problem exist i think from always.

Please solve this issue :)

Thanks!

Thanks for your report.

Can you send me an email, so I can send you back a development version of WinSCP for testing? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

I have a similar problem, If I lose the connection WinSCP tries to reconnect. But I cannot stop it or close the program. If I click the "X" it just restarts the connection, while it is trying to reconnect, it won't let me shut the program. This happens when "Keep remote directory up to date", but it might happen other time too.

When I use the task manager to shut it down, that won't work either. Task manager opens a window "this program is waiting for user input" but before I can do anything with that window, WINSCP ( i think ) forces it to close.

This issue has been added to the tracker:
https://winscp.net/tracker/1564

No amount of debugging versions is going to stop this. It is a fundamental "How it is written" issue in WinSCP. It has always done this, on all computers across versions, across different networks, for a long time (as in always). It's only the length of time it takes that differs. Expected behaviour: Click the cancel button, it exits as fast as your CPU can send the command. Actual behaviour: You click cancel and it can take anything from 15 seconds to a few minutes to simply trash a connection.

Danve wrote:

Takes a lot to cancel a stopped connection
Thanks

Same answer: Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Takes a lot to cancel a stopped connection
Thanks

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Hi,

If WinSCP is used for connect to a remote which is not response or spercified a wrong port, then users instantly close to connection.

Now, WinSCP will show "Cancelling..." but seem forever to done this task.

Please try host diaocsva.com with port 2283 for SFTP connection.

I have to use Task Manager to Close it!

Please fix this issue.

This happened in 5.1.4