Out of memory error when downloading large file #10206
Comments
Milestone renamed |
I cannot reproduce the issue. Downloading some GBs the memory usage of Cyberduck is always below 500MB. |
I will attempt to reproduce the error and report back my results. If I can reproduce the error, how would you like to proceed? Happy to arrange a time for you to remote into my machine to debug. |
I tried again to download a large file, and it occurred again. Cyberduck Version 6.4.6 (27773). MacOS 10.13.4 (17E199). Screenshot: https://trac.cyberduck.io/attachment/ticket/10206/Screen%20Shot%202018-04-17%20at%2011.02.23%20am.png |
I tried to replicate the issue with 6.6.2 and downloading a 12GB sparsebundle from B2. The memory consumption was in the normal range. Is there any chance to try again with version 6.6.2? Thanks. |
I had uploaded an 82GB sparsebundle to Backblaze B2 over 3 days. Once done, I then proceeded to download it to verify it had completed successfully. From memory I quit the app in-between, but I could be wrong.
I left that running for the day or so, for it to get 64.29GB through the download, before my operating system complained it ran out of memory, as well as disk space (despite having 130GB or so available at the time of the download). I opened activity monitor at it turns out that Cybderduck was taking up 77GB of memory, so that is a large swap file it would have had (I only have 16GB of memory).
Screenshot of the situation attached, as well as of the disk space error.
I ended up quitting cybderduck and restarting the computer. I tried to resume the transfer, however I then got a permissions error, screenshot attached.
Attachments
Screen Shot 2018-01-25 at 11.02.35 pm.png(1133.8 KiB)Screen Shot 2018-01-25 at 11.03.47 pm.png(119.8 KiB)Screen Shot 2018-01-25 at 11.25.02 pm.png(215.8 KiB)Screen Shot 2018-04-17 at 11.02.23 am.png(5393.1 KiB)The text was updated successfully, but these errors were encountered: