#8633 closed Bug report (fixed)
Freeze with 2 Servers "Limit number of simultaneous connections"
Reported by: | allesbesser | Owned by: | Tim Kosse |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Limit number of simultaneous connections | Cc: | allesbesser@… |
Component version: | Operating system type: | Windows | |
Operating system version: | Windows Vista Business SP2 (Build 6002) |
Description
Description:
FileZilla freezes when downloading multiple files with "Limit number of simultaneous connections" set to 1 from two servers when one file finishes.
Steps to reproduce:
- Open connections manager
- Add an FTP account, set "Limit number of simultaneous connections" to 1
- Add another FTP account, set "Limit number of simultaneous connections" to 1
- Connect to account 1
- Connect to account 2
- Start downloading at least two bigger files from server 1
- Start a download of at least one file from server 2 (while the queue on server one has at least one download that has not yet started)
- As soon as the download from server 1 finishes, FileZilla crashes.
Attachments (5)
Change History (15)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Status: | new → moreinfo |
---|
So what does it actually do? Does it freeze or does it crash? In case it freezes, does it recover after some time?
comment:3 by , 12 years ago
Status: | moreinfo → new |
---|
Sorry, it actually freezes but does not seem to recover.
comment:4 by , 12 years ago
Status: | new → moreinfo |
---|
When it freezes, can you open the task manager and check the CPU usage of FileZilla? Is it close to 100%? Or to 50% in case you have two cores? Or even close to zero?
So, how much CPU usage does FileZilla do when it is frozen? (And how many CPU/cores do you have?)
comment:5 by , 12 years ago
Cc: | added |
---|---|
Status: | moreinfo → new |
Interestingly about 30 to 40% on two cores and with each core having about the same, both only for FileZilla... please see attachments from ProcessExplorer (Taskmanger does not provide that much information).
comment:6 by , 12 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
Confirmed. Rather strange bug, looks like the queue repeatedly requests exclusive access to a connection, but always discards it when it gets it due to it being the wrong.
comment:7 by , 12 years ago
Summary: | Crash with 2 Servers "Limit number of simultaneous connections" → Freeze with 2 Servers "Limit number of simultaneous connections" |
---|
comment:8 by , 12 years ago
I see what the problem is: The queue has the ability to borrow browsing connections if said connection belongs to a site with a connection limit of one. That code was built with the assumption that there's at most one such connection. That was fine in the past, but is no longer a valid assumption since the addition of tabs.
comment:9 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Please try the upcoming 2013-05-13 build from http://filezilla-project.org/nightly.php
Reproducability:
Always