Invalid access to memory
In Options > Preferences > Transfer > Background:
- Tick the box for "Transfer each file individually on background by default"
- Set Maximal number of transfers at the same time to a number larger than 1
In your Session, be sure to connect using SFTP (without SCP fallback), a private Key file, no Password entry with Proxy configuration set to:
- Local
- Proxy command: plink -load jumpserver -nc %host:%port
Obviously, this requires that you have configured:
- A session to connect using a Private Key to a SSH server in Putty and gave this session the name "jumpserver"
- Pageant.exe has been added your private key
- Pageant.exe is running in the Task Tray with your private key loaded
It seems that either the agent or the jump session cannot handle multiple proxied parallel file transfers.
I have tried this in versions 4.x, 5.1, 5.6, 5.7 and the problem exists throughout.
The behaviour always starts with a server timeout, which when you then try to manually interrupt the queue results in the "Invalid access to memory".
Workaround, either one:
a) Deactivate single session background transfer for each transfer
or
b) limit transfers at the same time to 1
Obviously not great for network throughput, but at least stable. :)
WinSCP 5.9.3
Error message:
Invalid access to memory.
Stack trace:
(00854FE7)
(00866422)
(0086848A)
(00865244)
(000624F6) [77
Status: unknown_rel_addr
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.
- Tick the box for "Transfer each file individually on background by default"
- Set Maximal number of transfers at the same time to a number larger than 1
In your Session, be sure to connect using SFTP (without SCP fallback), a private Key file, no Password entry with Proxy configuration set to:
- Local
- Proxy command: plink -load jumpserver -nc %host:%port
Obviously, this requires that you have configured:
- A session to connect using a Private Key to a SSH server in Putty and gave this session the name "jumpserver"
- Pageant.exe has been added your private key
- Pageant.exe is running in the Task Tray with your private key loaded
It seems that either the agent or the jump session cannot handle multiple proxied parallel file transfers.
I have tried this in versions 4.x, 5.1, 5.6, 5.7 and the problem exists throughout.
The behaviour always starts with a server timeout, which when you then try to manually interrupt the queue results in the "Invalid access to memory".
Workaround, either one:
a) Deactivate single session background transfer for each transfer
or
b) limit transfers at the same time to 1
Obviously not great for network throughput, but at least stable. :)
WinSCP 5.9.3
Error message:
Invalid access to memory.
Stack trace:
(00854FE7)
(00866422)
(0086848A)
(00865244)
(000624F6) [77
Status: unknown_rel_addr
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.
