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

2nd connection to S3 causes strange looping #7387

cyberduck opened this issue Aug 7, 2013 · 1 comment

2nd connection to S3 causes strange looping #7387

cyberduck opened this issue Aug 7, 2013 · 1 comment


Copy link

@cyberduck cyberduck commented Aug 7, 2013

bb5aab6 created the issue

I'm not sure how much detail you need for this issue, but this is how I've replicated:

  1. Created an S3 account.
  2. Logged in providing my credentials.
  3. Uploaded a file (successfully) to some bucket.
  4. Clicked on "Disconnect" at the top-right.
  5. Re-open the connection from bookmarks list (same one)
  6. See all my buckets in a list.
  7. Try to expand any bucket.
  8. It hangs and I can see the status flickering from "9 files" to "(spinner) ..... directory (bucket name)" where (spinner) is an AJAX spinner and (bucket name) is the name of the bucket I'm trying to open and ...... is something I can't see because it's flickering so quickly.
  • Windows version: (7 Pro) 6.1 (Build 7601, SP1) x64
  • Cyberduck version: 4.3.1 (11008)

To fix this problem I close CyberDuck and re-open. But I can never successfully get to a 2nd S3 session after closing my first.

Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 18, 2013

@ylangisc commented

Please update to the latest snapshot build available and reopen this issue if it's still a problem. We have since
refactored many things in this area.


@cyberduck cyberduck closed this Sep 18, 2013
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants