Cyberduck Mountain Duck CLI

Opened on Jan 8, 2011 at 12:12:23 AM

Closed on Jan 10, 2011 at 11:46:35 AM

Last modified on Jan 10, 2011 at 5:30:29 PM

#5624 closed defect (fixed)

Maximum simultaneous transfer limit of 1 not properly handled

Reported by: ganwar Owned by: dkocher
Priority: normal Milestone: 4.0
Component: core Version: Nightly Build
Severity: major Keywords: maximum simultaneous
Cc: Architecture: Intel
Platform: Mac OS X 10.6

Description

I start one tranfer, then start several more. Initially, the maximum transfer limit of 1 is in effect, with the other transers waiting. However, if I stop one of the queued, non-open tranfers, another queued transfer starts. Thereafter Cyberduck behaves as if the maximum transfer limit is 2, until all transfers are complete or stopped and removed from the transfers list.

3.6.* versions didn't exhibit this behavior, but versions 3.8 and higher (including the latest nightly build) do.

Change History (3)

comment:1 Changed on Jan 8, 2011 at 1:03:23 PM by dkocher

  • Milestone set to 4.0
  • Owner set to dkocher
  • Status changed from new to assigned

comment:2 Changed on Jan 10, 2011 at 11:46:35 AM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r8220.

comment:3 Changed on Jan 10, 2011 at 5:30:29 PM by dkocher

You can switch to the latest snapshot build that includes the fix.

Note: See TracTickets for help on using tickets.