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

Temporary files created during transfers are not cleaned up automatically #7778

Closed
cyberduck opened this issue Feb 7, 2014 · 9 comments
Closed

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 7, 2014

dcebe47 created the issue

I choose to display hidden files in Windows by default. Each time a transfer is initiated in Cyberduck, a temporary file is created on my Desktop. That file is not cleaned up even after the transfer is finished until I manually hit F5. Any way to address this?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 8, 2014

dcebe47 commented

I would like to suggest to keep temporary files off the Desktop completely, because they interfere with the placement of other icons. Perhaps temporary files can be stored either in the Cyberduck directory or one of the Windows temp directories, and the user can be given a choice.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 18, 2014

16edd33 commented

I would like to also support keeping all temporary files away from the desktop or any non-temporary folder.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 26, 2014

@dkocher commented

#7770 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2014

@ylangisc commented

Windows drag&drop mechanics does not allow source application of drag&drop operation to easily find out where the files are dropped. That why we have a filesystem watcher and create a temporary file at the drop location to find out the drop folder. There is no easy way to change this. A shell extension might be a solution but needs a major refactoring.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2014

dcebe47 commented

I don't understand the comment by yla. Cyberduck creates a temporary file during a transfer, and the temporary file remains there even after Cyberduck is closed. That's not normal behavior. If you know where the temp file is created, then you know where to remove it from.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2014

16edd33 commented

Replying to [comment:6 Knocks]:

I don't understand the comment by yla. Cyberduck creates a temporary file during a transfer, and the temporary file remains there even after Cyberduck is closed. That's not normal behavior. If you know where the temp file is created, then you know where to remove it from.

I think yla might be a bit confused. The actual issue is not that the file is not removed, but that windows seems to think it is there until there is a manual refresh. It might be a windows problem, but I suspect there might a way to fix it within Cyberduck.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 4, 2014

@dkocher commented

We cannot reproduce the issue that the Desktop in Explorer must be manually refreshed.

Loading

@cyberduck cyberduck closed this Apr 4, 2014
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 4, 2014

dcebe47 commented

dkocher: Are you using Windows 8.1 x64?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 5, 2019

96cb5ac commented

I'm using windows 10 x64

When I use the "duck --longlist" key temp files are created

When I use the "duck --delete" key temp files are created

When I use the "duck --upload" key temp files are created

Temporary files are not automatically deleted when the program cyberduck is finished

After one night of work 5GB of temporary files were formed.

I Have to remove them manually.

Because the files are very shallow the deletion takes a very long time.

I hope this can be fixed somehow?

Loading

@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