Custom Query (8164 matches)


Show under each result:

Results (445 - 447 of 8164)

Ticket Resolution Summary Owner Reporter
#944 Latest client hangs while busy. Alexander Schuch twoseven

Just testing out the 2.2.15 client along side the previous version. The setup is two laptops plugged directly into a 100mb/s switch into the server running filezilla server 0.9.10.

When I upload a directory with about 13000 files (700 folders - 390mb) in it the client hangs for about 30 seconds and 'not responding' appears in the title bar. (In case someone is wondering, I was moving a s/w application to another machine)

It then proceeds to list every file in the directory that is to be copied and all sub-directories in the 'remote site' window, which takes approx. another minute, then queues up every file in the process queue taking a further minute (if it takes too long the server times out the connection and it requires the operation to be restarted). It then copies all the files to the server as would be expected. It should not be auto-listing files in the remote window - this is both bad usability and costely in CPU cycles for no reason.

If I delete the directory on the server (via the client remote site window), it then lists out the contents of all the subdirectories in the remote window, again taking ages, then queues them up, then issues a DEL command for every single file - the whole process took 15 mins where all that was needed was a DEL command to be issued on the root directory (the one I selected) and the OS should have done the rest.

When I use the previous version, it does not list out all the files in the remote site window before adding them to the process queue. It also takes less time to do the transfer (perhaps there is a config change or something)

So there are two problems. First, it takes a huge amount of time simply to copy a directory full of files (locking up filezilla), and second why are actions not offloaded to the OS (such as delete the directory, rather than every file individually).

As a comparison, zipping the directory in winzip took 2 mins, Ftp'ng the resulting 190mb file to the server took 1 min and deleting it took half a sec. There is enough information in the windows file system to tell you it was a large transfer and compression is needed - why not use it.

Also, if configurations changes are being made between versions, please list them in a readme as well as bugfixes etc.

#11198 rejected Startup error message Warren Montgomery

I have had far too many updates and this startup message will not go away. Is there a way to get rid of it?

Screenshot attached.

FileZilla Client

Version: 3.24.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-unknown-linux-gnu Build date: 2017-02-21 Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1 Compiler flags: -g -O2 -Wall -std=gnu++14

Linked against:

wxWidgets: 3.0.3 GnuTLS: 3.5.8 SQLite: 3.16.2

Operating system:

Name: Windows 8.1 (build 9600), 64-bit edition Version: 6.3 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq bmi2 Settings dir: C:\Users\Warren\AppData\Roaming\FileZilla\

#7939 outdated Empty directory listing bug Sergey

I've got the following trouble in all FileZilla versions i had used including the latest (3.5.3)

Empty directory listing doesn't work properly (in both passive and active mode). When i try to open an empty directory or upload a file in an empty directory opening or upload fails in most cases (about 85% – sometimes, seemingly randomly, it passes).

I presume that this is server-related trouble but since the server is a popular public host with very "standard" settings the trouble could be resolved. Some other FTP-client (but not all) are working properly with this server

In the attachment is the log of uploading the file in an empty directory.

Below is my system parameters:

Windows 7 64-bit AMD Athlon 64 X2

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.