-
-
Notifications
You must be signed in to change notification settings - Fork 297
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 issue with v8.1.1 on macOS Monterey 12.1 on a 13" MacBook Pro M1 #12695
Comments
(Phff, Deutsch ist so anglisiert. /s) I'm using x86 Monterey (16 GiB RAM) for a 94 GiB ftp job (~100k directories, ~1m files). It's currently at 49.58 GiB virt size, 1 GiB RSS, and 51 GiB of swap. There's minimal memory pressure otherwise. The issue started after the initial directory scan and it's going up slightly as the job progresses. Basic CS math says, even at 2m files with a whopping 256 bytes per file or dir structure on 64-bit platforms, it shouldn't use more than 0.5 GiB of RAM. Anything over 1 Gig for that is likely a bug. Looks like one or more memory leaks. It's difficult to say what is and is not the same bug. It probably needs profiling. |
I did a large transfer yesterday of approx. a 100 GB collection of files & folders and noticed this runaway memory usage as well. I would stop the transfer and allow the swap usage to clear up and start again every 10-15 GB transferred. This is Monterey 12.1 on an M1 MacBook Air. |
Lower memory pressure when submitting many tasks with limited queue s…
Unfortunately, I am using 8.3.2 and still encountering this error. Monterey 12.3.1, MacBook Pro (M1 Pro), Cyberduck version 8.3.2 (37449). I am downloading 10's of GB from S3, typically larger files (either 250kb or 20 MB). |
Duplicate for #12695. |
(Sorry, it is in German, but I guess you can figure it out anyways.)
I connected via OpenStack Swift Keystone 3 and tried to download a 100GB file.
Reading through other issues regarding memory hogging, I tried the transfer with deactivated segmented transfer option, which did not bring any improvement.
The text was updated successfully, but these errors were encountered: