[Cyberduck-trac] [Cyberduck] #10564: Large jobs take a long time after the last transfer to be marked as finished

[Cyberduck]

#10564: Large jobs take a long time after the last transfer to be marked as
finished
--------------------------+------------------------
    Reporter:  sebastian  |      Owner:
        Type:  defect     |     Status:  new
    Priority:  normal     |  Milestone:
   Component:  core       |    Version:  6.8.3
    Severity:  normal     |   Keywords:
Architecture:  Intel      |   Platform:  Windows 10
--------------------------+------------------------
 When uploading or downloading a large job (e.g. a directory containing
 5000 files, 75 GB in total) to/from an '''S3-cryptomator-vault''', it
 takes very long (up to one hour and more) until the job is actually marked
 as ''finished''. The CPU load during this phase is high.

 It can be observed within ''CyberDuck'' and ''Duck.sh'', on Windows and on
 Linux (I can not test on a Mac).

 It makes queuing jobs impossible, because the job still counts as active.

 The message that is displayed while nothing is being transferred but the
 job is still unfinished looks like this (note the missing ''?? minutes
 remaining'' phrase):
 {{{
 [▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮] 71.4 GiB (76,687,296,696 bytes) of 71.4
 GiB (100%, 2.6 MB/sec)
 }}}

--
Ticket URL: <https://trac.cyberduck.io/ticket/10564>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows