Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#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:

  1. Open connections manager
  2. Add an FTP account, set "Limit number of simultaneous connections" to 1
  3. Add another FTP account, set "Limit number of simultaneous connections" to 1
  4. Connect to account 1
  5. Connect to account 2
  6. Start downloading at least two bigger files from server 1
  7. 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)
  8. As soon as the download from server 1 finishes, FileZilla crashes.

Attachments (5)

3.png (14.9 KB) - added by allesbesser 7 years ago.
System Information
1.png (22.9 KB) - added by allesbesser 7 years ago.
System CPU
2.png (12.0 KB) - added by allesbesser 7 years ago.
FileZilla CPU
4.png (16.0 KB) - added by allesbesser 7 years ago.
FileZilla Threads
5.png (17.7 KB) - added by allesbesser 7 years ago.
FileZilla Performance

Download all attachments as: .zip

Change History (15)

comment:1 Changed 7 years ago by allesbesser

Reproducability:

Always

comment:2 Changed 7 years ago by Alexander Schuch

Status: newmoreinfo

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 Changed 7 years ago by allesbesser

Status: moreinfonew

Sorry, it actually freezes but does not seem to recover.

comment:4 Changed 7 years ago by Alexander Schuch

Status: newmoreinfo

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?)

Changed 7 years ago by allesbesser

Attachment: 3.png added

System Information

Changed 7 years ago by allesbesser

Attachment: 1.png added

System CPU

Changed 7 years ago by allesbesser

Attachment: 2.png added

FileZilla CPU

Changed 7 years ago by allesbesser

Attachment: 4.png added

FileZilla Threads

Changed 7 years ago by allesbesser

Attachment: 5.png added

FileZilla Performance

comment:5 Changed 7 years ago by allesbesser

Cc: allesbesser@… added
Status: moreinfonew

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 Changed 7 years ago by Tim Kosse

Owner: set to Tim Kosse
Status: newaccepted

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 Changed 7 years ago by Tim Kosse

Summary: Crash with 2 Servers "Limit number of simultaneous connections"Freeze with 2 Servers "Limit number of simultaneous connections"

comment:8 Changed 7 years ago by Tim Kosse

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 Changed 7 years ago by Tim Kosse

Resolution: fixed
Status: acceptedclosed

Please try the upcoming 2013-05-13 build from http://filezilla-project.org/nightly.php

comment:10 Changed 6 years ago by allesbesser

Sorry for the late reply. Just came back. Perfect. Works now.

Note: See TracTickets for help on using tickets.