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
Since v.4 I notice that if I download, even only with a single file, (I do it via drag and drop from the browser) cyberduck has for 2-3 seconds >100% CPU load and I get the wait-beach-ball-cursor for that period.
With the time this gets annoying in everyday use.
Macbook Pro, OS 10.6.7, v. 4.0.3.
The text was updated successfully, but these errors were encountered:
But ... deleting the Transfers launched >1000 Threads and and resulted in 100% CPU load for over an hour! At least I consider that not as normal. A possibility to limit the amount of thinks kept in the history of transfers thus would be very appreciated. At least for the stuff of the transfers that causes these problems. A ordinary independent log file for the transfers would be nethertheless nice.
Since v.4 I notice that if I download, even only with a single file, (I do it via drag and drop from the browser) cyberduck has for 2-3 seconds >100% CPU load and I get the wait-beach-ball-cursor for that period.
With the time this gets annoying in everyday use.
Macbook Pro, OS 10.6.7, v. 4.0.3.
The text was updated successfully, but these errors were encountered: