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

Memory leak when downloading from S3 #15927

Open
alaz opened this issue May 13, 2024 · 2 comments
Open

Memory leak when downloading from S3 #15927

alaz opened this issue May 13, 2024 · 2 comments
Labels
s3 AWS S3 Protocol Implementation

Comments

@alaz
Copy link

alaz commented May 13, 2024

This ticket system is to report bugs and feature requests. For support, visit the help page first.

  • If you have trouble connecting to a server or your login credentials are not valid, try to resolve the issue with the assistance of your hosting service provider. Any such ticket will be closed with a resolution of thirdparty.

Describe the bug

Hi, I was downloading a 30GB sparsebundle from S3 and Cyberduck consumed 75GB of memory, please see a screenshot below.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Screenshot 2024-05-12 at 21 29 10

Desktop (please complete the following information):

  • OS: macOS 14.4.1
  • Version 8.8.2

Log Files

Sorry, no log file, I have disabled them.

Additional context
Add any other context about the problem here.

@alaz
Copy link
Author

alaz commented May 13, 2024

Possibly a duplicate of #15510 and #15900

@dkocher dkocher added the s3 AWS S3 Protocol Implementation label May 14, 2024
@kdambiec
Copy link

I've had the same issue multiple times over the last year with Cyberduck on Mac. It also occurs with SFTP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

3 participants