Page 1 of 1

writing files on local harddisk

Posted: 2020-04-25 10:40
by ffprins
By downloading files from Service Provider to local PC FileZilla stops writing to local harddisk.
Big files (I copied a file of 19GB) are going well, but the download of my Joomla website (a lot of small files) breaks off.
I tried it several times in several days. My Service Provider tested it for me and had the same problem. His advice: wait for a FileZilla update.
I did this copy activity a lot of times before without problems.
Now I used -for the time being- WinSCP (but slow!).
Hope you will find the bug and solve it.

My PC:
Windows 10, version 2004 - build 19041.207
FileZilla Client, version: 3.47.2.1

Re: writing files on local harddisk

Posted: 2020-04-27 08:29
by botg
What exactly do you mean by "download [...] breaks off"?

Re: writing files on local harddisk

Posted: 2020-04-29 08:56
by ffprins
FileZilla continues reading files and putting them in the buffers, but FilzeZilla doesn't write the files to the local harddisk.
So the buffer grows until all the files are read, but the writing activity stops (after a minute of less).

Re: writing files on local harddisk

Posted: 2020-04-29 11:10
by botg
What buffer?

Re: writing files on local harddisk

Posted: 2020-04-30 08:32
by ffprins
If you prefer the Dutch word? (I am Dutch)
*Wachtrij*
I think that buffer is the translation for that in English.
Maybe it's an other word.
Maybe it's *queue*
In the last FileZilla Client update, version 3.48.0, the problem is not yet solved.

Re: writing files on local harddisk

Posted: 2020-05-12 11:30
by boco
How is the process actually started? What happens if you press the "Process queue" button in the toolbar again?

Re: writing files on local harddisk

Posted: 2020-05-21 10:20
by ffprins
Q (boco): How is the process actually started?
A (ffprins): By selecting files and chose 'download files'

Q (boco): if you press the "Process queue" button in the toolbar again?
A (ffprins): Then there happens nothing.

In version 3.48.1 my problem is not yet solved :-(