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

Syncing folder with Cloudspace makes Cyberduck crash #6177

Closed
cyberduck opened this issue Aug 27, 2011 · 1 comment
Closed

Syncing folder with Cloudspace makes Cyberduck crash #6177

cyberduck opened this issue Aug 27, 2011 · 1 comment
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

Th Heiserowski created the issue

I had this behaviour twice today. The third time I was trying to synchronize I cancelled the process as described below.

What I am doing:

  • log into my cloud space (Hosteurope)
  • select the cloud space bucket and say "synchronize"
  • select a local folder (contains about 50 folders including subfolders, each folder contains about 10 files)
  • synchronize

What I am observing:

  • Cyberduck opens each folder to see if new files are available
  • since only five new folders are there, the other 45 are discarded (takes about 3-5 minutes)
  • Cyberduck finds a folder that has been synchronized today (called "SomeFolder") and which has been uploaded completely
  • Cyberduck starts creating subfolders of "SomeFolder" each of which is named "SomeFolder" again > each of these subfolders is empty
  • the transfer window constantly shows "Creating folder SomeFolder"
  • the memory usage constantly rises > it started at about 130 MB and grew to 1,1 GB where I canceled the upload
  • CPU usage was at 130% (1,83 GHz Core 2 Duo) then whereas it was at about 40% during the search for a new folder

This may be similar to the problem described in ticket #6170.

I sent two crash reports today using Cyberduck's internal crash report service.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please try the latest snaphot 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 s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants