Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop file transfer doesn't stop waiting transfer and starts next one #4325

Closed
cyberduck opened this issue Mar 22, 2010 · 1 comment
Closed

Stop file transfer doesn't stop waiting transfer and starts next one #4325

cyberduck opened this issue Mar 22, 2010 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 22, 2010

6a9d246 created the issue

I had 6 transfers (call them f1-f6). I have my max connections set to 1, so only f1 was transferring, the others were waiting.

I decided I didn't want f6, so I clicked on it then clicked Stop. Instead of stopping it, f2 started transferring, so I now had 2 transfers going at once (despite a max transfers of 1). f6 still shows as waiting, and I can't remove it from the list.

In addition, when f1 finished, f2 was still transferring, but it started f3 transferring, against despite a max transfers of 1.

I then tried stopping f6 again. Now it says Disconnecting , but I still can't remove it from the list, and f4 started, so I now have 3 transfers going.

It appears that whenever a transfer ends, either because it's finished or I stop a queued transfer (even if the stop doesn't work), Cyberduck just starts the next transfer. It seems it should check the max transfers before starting a transfer and not start it if max transfers would be exceeded.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 6, 2010

@dkocher commented

Duplicate for #3011. Thanks for the detailed description of the bug.

Loading

@cyberduck cyberduck closed this Aug 6, 2010
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants