<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.17.2
Error message:
Invalid access to memory.
Stack trace:
(00422DDC)
(00F85292)
(00F872FA)
(00F840B4)
(00087D7F) ntdll.dll
(00073221) ntdll.dll.KiUserExceptionDispatcher
(0044553D)
(00450F8D)
(0001B464)
(0001AD21)
(000A9DCB)
(0042598E)
(00424F2E)
(00043449) USER32.dll
(00023F87) USER32.dll
(00023B25) USER32.dll
(0002D16D) USER32.dll
(000731DB) ntdll.dll.KiUserCallbackDispatcher
(00028EFB) USER32.dll.PeekMessageW
(0023D2BC)
(00E31C25) @@Symlink@Finalize
(00E31289) @@Symlink@Finalize
(0001AA19)
(0004FD63)
(00047BB2)
(003E7F9C)
(001C6B85)
(003A4578)
(00043449) USER32.dll
(00023F87) USER32.dll
(000230D9) USER32.dll
(00022EBB) USER32.dll.DispatchMessageW
The problem happens rarely. I cannot reproduce it.
Great work, this error no longer occurs. Thank you very much for help. You saved my day :)
If I encounter any complications in the future, I will post on the forum. I am positively surprised by your work. Best regards
Thank you so much. I will try this version. Regards ;)
Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
Keeping remote directory up to date function. The program only updates the open visible folder. Detects changes in subfolders, but sends nothing, suspends the entire function.
WinSCP 5.16.1
Error message:
Invalid access to memory.
Stack trace:
(0001E641)
(00F82F96)
(00F84FFE)
(00F81DB8)
(00087D6F) ntdll.dll
(00073211) ntdll.dll.KiUserExceptionDispatcher
(00DA128F)
(00D9B386)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
(00F83601)
(00F84BDB)
(00D9B3D1)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
(0001E641)
(00F82F96)
(00F84FFE)
(00F81DB8)
(00087D6F) ntdll.dll
(00073211) ntdll.dll.KiUserExceptionDispatcher
(00DA128F)
(00D9B386)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
(00F83601)
(00F84BDB)
(00D9B3D1)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
(0001E641)
(00F82F96)
(00F84FFE)
(00F81DB8)
(00087D6F) ntdll.dll
(00073211) ntdll.dll.KiUserExceptionDispatcher
(00DA128F)
(00D9B386)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
(00F83601)
(00F84BDB)
(00D9B3D1)
(0001B268)
(0001ACF1)
(000A9B43)
(004254AA)
(00424A4A)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024C55) USER32.dll
(0002D62D) USER32.dll
(000731CB) ntdll.dll.KiUserCallbackDispatcher
(0002B45B) USER32.dll.PeekMessageW
(0023CDD8)
(00E2FC99) @@Symlink@Finalize
(00E2F2FD) @@Symlink@Finalize
(0001A9E9)
(0004FB4B)
(00047B46)
(003E7AB8)
(001C66A1)
(003A4094)
(00043749) USER32.dll
(000250B7) USER32.dll
(00024209) USER32.dll
(00023FCB) USER32.dll.DispatchMessageW
I know how to reproduce the problem or the problem happens frequently enough. I wish to be contacted by the WinSCP team to help resolving the problem.