Invalid access to memory

I have never received the below problem before so I can't report it in any great detail, this just happened when I woke up. However, using the newer versions of WinSCP (started 2-3 versions ago?) I am getting frequent crashes if I make a new directory and try and go in it on a slow connection - before the directory is actually made - this is repeatable. I believe it also happens if you try to change directories while a transfer is occurring. This only happens when the directory is not already cached.
Best regards,
Jon Eyrick


<Try to describe precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.)>
<If relevant, consider attaching a session log file or a screenshot)>

WinSCP 5.6.5

Error message:
Invalid access to memory.

Stack trace:
[009FFACD] TMessageTimeout::DoTimer
[77D6B466] ntdll.dll
[77D2012E] ntdll.dll.KiUserExceptionDispatcher
[00CA0060] System::Classes::_18201
[76D96235] USER32.dll
[76D968E5] USER32.dll
[76D97D2C] USER32.dll
[76D97DF5] USER32.dll.DispatchMessageW

jaggedsoft@gmail.com wrote:

I have never received the below problem before so I can't report it in any great detail, this just happened when I woke up.

So assume you are not able to reproduce it? Or are you?

However, using the newer versions of WinSCP (started 2-3 versions ago?) I am getting frequent crashes if I make a new directory and try and go in it on a slow connection - before the directory is actually made - this is repeatable. I believe it also happens if you try to change directories while a transfer is occurring. This only happens when the directory is not already cached.

This bug is being tracked already:
https://winscp.net/tracker/1272
I have sent you an email with a dev version of WinSCP for testing.

<Try to describe precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.)>
<If relevant, consider attaching a session log file or a screenshot)>

WinSCP 5.7.7

Error message:
Invalid access to memory.

Stack trace:
(0009F7F5) TMessageTimeout::DoTimer
(0008A63F) ntdll.dll
(00077E9A) ntdll.dll.KiUserExceptionDispatcher
(0034059C) System::Classes::_18201
(000374F1) USER32.dll
(00015C3B) USER32.dll
(0001553C) USER32.dll
(000152FB) USER32.dll.DispatchMessageW

The problem happens rarely. I cannot reproduce it.