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.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

GieltjE

Latest crash information logs sent via email.
martin

Thanks for your feedback. I'm sending you a new debug build.
GieltjE

Still occurs, attached is the latest log.
GieltjE

Thanks for the new test build, testing has begun.
martin

Re: Invalid access to memory.

This bug has been added to the tracker:
https://winscp.net/tracker/1606

I'm sending you an email with a development version of WinSCP.
martin

Re: Invalid access to memory.

andylemmon wrote:

I also experienced the "invalid access to memory" WinSCP ver 576 on Windows 10.
It gave me some type of timeout error while I was deleting a directory on the left side user panel.

Can you reproduce the problem with the latest version of WinSCP? If you can please, post a separate report as this seems unrelated.
martin

GieltjE wrote:

Managed to reproduce it, took some time reproduce it, hope the attached file helps.

Thanks. Will contact you in few days.
andylemmon

Re: Invalid access to memory.

GieltjE wrote:

Using DotNet 4.7.1 on X64 platform with WinSCP 5.12.1-beta during PutFiles to an OpenSSH 7.6 (SFTP) host it crashes quite often (see attached log).

This usually happens if there is a delay between files.


I also experienced the "invalid access to memory" WinSCP ver 576 on Windows 10.
It gave me some type of timeout error while I was deleting a directory on the left side user panel. Then this error:
Stack trace:
(0070F590) TTerminal::GetIsCapable
(00088D2F) ntdll.dll
(0006FBF1) ntdll.dll.KiUserExceptionDispatcher
(003823D8) System::Actions::TContainedActionList::UpdateAction
(00169ECE) Vcl::Actnlist::TCustomAction::Update
(001DBD36) Vcl::Forms::_16777
(001DBDB4) Vcl::Forms::TCustomForm::UpdateActions
I had to shut WinSCP down via Task Manager as the error window was in loop I could not break out of.
GieltjE

Managed to reproduce it, took some time reproduce it, hope the attached file helps.
GieltjE

So far haven't been able to reproduce the problems with the new build (but I have been on vacation the past week so not much testing was done).

Will report in a few days
martin

GieltjE wrote:

Got another message: "Assertion failed: FPendingActions->Count == 0, file core\SessionInfo.cpp, line 1438", doesn't seem to be related to this bug though.

1) Were you able to reproduce the original problem with the new build?

2) Please send a log for the new problem too.
GieltjE

Got another message: "Assertion failed: FPendingActions->Count == 0, file core\SessionInfo.cpp, line 1438", doesn't seem to be related to this bug though.
GieltjE

Finally got one, sending it via mail after compression (it's quite large).

-Edit- Sent it via wetransfer, your mailserver wouldn't accept the filesize.
martin

Re: Invalid access to memory.

GieltjE wrote:

Thanks, have been testing it but cannot seem to crash it again (with the mentioned build it used to be a 70% crash rate), could it be that this one contains some additional patches?

Not really.
So can you at least post a session log file from the official version (when it crashes)?
GieltjE

Re: Invalid access to memory.

martin wrote:

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.


Thanks, have been testing it but cannot seem to crash it again (with the mentioned build it used to be a 70% crash rate), could it be that this one contains some additional patches?
martin

Re: Invalid access to memory.

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.
GieltjE

Invalid access to memory.

Using DotNet 4.7.1 on X64 platform with WinSCP 5.12.1-beta during PutFiles to an OpenSSH 7.6 (SFTP) host it crashes quite often (see attached log).

This usually happens if there is a delay between files.