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

Application instances do not quit #6390

Closed
cyberduck opened this issue Nov 25, 2011 · 1 comment
Closed

Application instances do not quit #6390

cyberduck opened this issue Nov 25, 2011 · 1 comment
Assignees
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

38a28fd created the issue

Hi!

Cyberduk very often remain in memory, after I close application. I see in taskmanager. Sometimes I see 4-5 Cyberduck.exe lines in taskamanger.

Example:

  1. Start cyberduck
  2. Connect Amazon S3 via bookmark, I type password (I dont know keychain is safe or not)
  3. Select my bucket
  4. Upload, I select three files.
  5. After transfer is success, I close trasfer window via "X".
  6. Main window, file/exit

Cyberduck exe remain in memory.

I remember this is old problem, now tested with 9319 version.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #6511. Please update to the latest snapshot build available.

@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.
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants