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

martin

Re: Very Large File Downloads

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Guest

I don't see that happening with WinSCP by default. RAM usage isn't going up and the OS shows storage usage during transfer.

Maybe its related to how the OS is setup or something? I can only think of some most likely not used here situations like a RAM disk.

I would expect here instead that those memory errors be just a coincidence and you have something else going on.

At least that's what I get from your post. Maybe Martin will see something different?
MGood1

Very Large File Downloads

We use WinSCP (version 5.19.2) via command lines in PowerShell scripts to download very large (multiple GB) files via FTP. It appears to hold the whole file in system memory as it is downloading and so we hit intermittent system memory errors when multiple processes are running. Is it possible to set up WinSCP so that it streams large files directly to disk rather than holding it in system RAM?