Opened 10 years ago

Last modified 10 years ago

#9031 new Bug report

When selecting the next file to download, only the remainder of the queue is searched

Reported by: Chris P Owned by:
Priority: low Component: FileZilla Client
Keywords: Priority scanning queue Cc:
Component version: Operating system type: Windows
Operating system version: 7 Home


I create a queue, it starts downloading, and then I set file priorities. What I mean is: while the queue is downloading, I change the priorities of files. I end up with something like:

file1 low - waiting
file2 highest - waiting
file3 medium - downloading- I only recently set file2 to highest
file4 low - waiting
file5 high - waiting
file6 low - waiting

However when file3 finishes, the next file to be downloaded is file5, NOT file2. It seems Filezilla is only scanning the remainder of the queue when picking the next file to download, rather than the whole queue.

Change History (4)

comment:1 by Alexander Schuch, 10 years ago

Status: newmoreinfo

Which version of FileZilla are you using?

comment:2 by Chris P, 10 years ago

Status: moreinfonew

FileZilla Client

Version: 3.7.3

Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2013-08-07
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12
GnuTLS: 3.1.11

Operating system:

Name: Windows NT 6.1 (build 7601, Service Pack 1)
Version: 6.1
Platform: 64 bit system

Sorry, silly oversight to miss this. I think I've seen this behaviour on prior versions too.

comment:3 by Chris P, 10 years ago

I have noticed another detail to this bug.

If there are two downloads (or uploads) happening at the same time, each scans the rest of the list from its own position. Ie, if a download is near the bottom of a queue and finishes, it will start on the highest priority entry of those physically below it in the queue. If another download further up the queue ends, it will scan all those entries below it in the queue.

comment:4 by Chris P, 10 years ago

file 1 -- priority Highest
file 2 -- downloading
file 3 -- priority High
file 4 -- downloading
file 5 -- priority Low
file 6 -- priority Medium

When file 4 finishes, it will start on file 6. When file 2 finishes, it will start on file 3. (My opinion is that both should scan the entire queue when they finish, and when either finish, file 1 should be started, not 3 or 6.)

Note: See TracTickets for help on using tickets.