-
-
Notifications
You must be signed in to change notification settings - Fork 279
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
Using >170Gb of memory and then crashing to download large folders from a server #15510
Comments
Possible duplicate of #15488. What's the protocol you are using? Any chance to follow the steps in #15488 (comment) and provide a screenshot when reproducing the issue (memory >2GB)? |
Thanks @tristanmcguire for the screenshots. As I'm not able to reproduce the issue I rely on the reporters to provide the information needed to find the cause. So, it would be great to also get a VisualVM screenshot from such a situation. |
I've also encountered this issue quite often on Mac so had to switch from Cyberduck to a different application. |
To get a VisualVM screenshot would be very helpful to track down the issue as I'm not able to reproduce the issue. |
This is a bug. I use a MacStudio, with M1 Ultra processor.
Instead of writing the data on my harddrive, it seems that it is trying to store it in the memory of the computer.
![cyberduck bug](https://private-user-images.githubusercontent.com/20067231/294319202-c47559f8-f036-4a67-a55c-a1ad5116e3f4.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk4MDIzMDUsIm5iZiI6MTcxOTgwMjAwNSwicGF0aCI6Ii8yMDA2NzIzMS8yOTQzMTkyMDItYzQ3NTU5ZjgtZjAzNi00YTY3LWE1NWMtYTFhZDUxMTZlM2Y0LmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAxVDAyNDY0NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFkNDEzNjlmYTc5NTkwMzE1NzExNGQ0ZWE5N2RhMTAzYTdiODkzY2JlY2RhMmZhNTA2ODJmN2I5YjRkZmY1M2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.uYnK-U-UVqOo-cAfFGqmIezk1HOipVdcbdTrYcDQGo4)
The text was updated successfully, but these errors were encountered: