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
Describe the bug
When trying to upload a document to a server folder I open file then upload and select the pdf file I choose to upload. I select upload then the cyberduck screen goes black says its not responding then crashes
To Reproduce
Steps to reproduce the behavior:
Go to 'file' then "upload"
Click on 'desired file i want to upload'
select upload
See error cyber duck crashes
Expected behavior
file is supposed to be uploaded in the folder then when i reopen cyber duck and connection the file should be accessible
Desktop (please complete the following information):
OS: Windows 10 pro
Version 8.9.0 (41543)
The text was updated successfully, but these errors were encountered:
These are the images of what happens when trying to upload the file
Below is the changes I've made to increase the UserProcessHandleQuota however still get the same crash
Does this happen as well when you unset Preferences/Transfers/"Bring window to front when transfer starts"?
You may try to update to the latest snapshot, which has a rewritten Transfers-window to combat the increased control count of Cyberduck - which may help reduce the overall number of handles requested.
1.3 GiB of free memory out of 8 GiB shouldn't be an issue.
Windows 10 (18363, 2019)
638544017860456838.txt
638544019322600398.txt
638544019323616875.txt
Describe the bug
When trying to upload a document to a server folder I open file then upload and select the pdf file I choose to upload. I select upload then the cyberduck screen goes black says its not responding then crashes
To Reproduce
Steps to reproduce the behavior:
Expected behavior
file is supposed to be uploaded in the folder then when i reopen cyber duck and connection the file should be accessible
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: