You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there's a serious issue in Cyberduck that keeps one from downloading large contents from an online-only OneDrive vault (maybe others, too).
I've tried to download 50 GB of data. It started downloading but after approx 2 hours the system got sluggish and reported that there's not enough memory.
When the download starts then Cyberduck's memory usages rises and rises. You can easily see that in terminal using "top" as command.
It seems that buffers are not cleared properly.
Please analyze and fix this accordingly.
Thanks and best regards,
rootie
The text was updated successfully, but these errors were encountered:
I've downloaded the previous version Cyberduck 7.3.0.32621 and can confirm that it WORKS there. Hence this must have been introduced with 7.3.1.
I'm quite sure that this memory fix does not work properly. With the old version the RAM memory usage stays < 500 MB during the whole download and does not increase permanently. It seems that every MB that Cyberduck is downloading with 7.3.1 is added to the RAM usage.
Small update: The RAM usage DOES increase with CyberDuck 7.3.0.32621 but not close as much as with 7.3.1. After downloading 17.5 GB from the online-only vault (OneDrive) CyberDuck 7.3.0.32621 consumes about 2,5 GB of RAM.
Hi,
there's a serious issue in Cyberduck that keeps one from downloading large contents from an online-only OneDrive vault (maybe others, too).
I've tried to download 50 GB of data. It started downloading but after approx 2 hours the system got sluggish and reported that there's not enough memory.
When the download starts then Cyberduck's memory usages rises and rises. You can easily see that in terminal using "top" as command.
It seems that buffers are not cleared properly.
Please analyze and fix this accordingly.
Thanks and best regards,
rootie
The text was updated successfully, but these errors were encountered: