[Cyberduck-trac] [Cyberduck] #3316: Excess CPU use when application should be completely idle

[Cyberduck]

#3316: Excess CPU use when application should be completely idle
---------------------------+------------------------------------------------
 Reporter:  Mly@…          |       Owner:  dkocher
     Type:  enhancement    |      Status:  new    
 Priority:  normal         |   Milestone:         
Component:  core           |     Version:  3.2    
 Severity:  normal         |    Keywords:         
---------------------------+------------------------------------------------

Old description:

> Cyberduck (v 3.2 4648) has two windows open, both simple
> FTP (port 21, one anonymous, one non-anonymous).  These
> connections are -- or should have been -- idle for several
> DAYS.  All I'd done after opening the connections was to list
> a directory and then hide the application.
>
> The Cyberduck application windows were in the background
> ("Hide" from Dock menu) and the application had not been selected
> as a foreground application for several days.
>
> Yet I see cyberduck.app consuming up to 7% CPU -- which matters on a
> battery-powered laptop -- to do *nothing*.
>
> Perhaps this is just a bad Java implementation, but perhaps there's
> something in the Cyberduck application which can be fixed.
>

>

> PS it is absolutely unreasonable that this trac software requires cookies
> JUST TO SUBMIT A FORM.  Stupid stupid stupid!  (But not dkocher's fault.)

New description:

 Cyberduck (v 3.2 4648) has two windows open, both simple FTP (port 21, one
 anonymous, one non-anonymous).  These connections are -- or should have
 been -- idle for several DAYS.  All I'd done after opening the connections
 was to list a directory and then hide the application.

 The Cyberduck application windows were in the background ("Hide" from Dock
 menu) and the application had not been selected as a foreground
 application for several days.

 Yet I see cyberduck.app consuming up to 7% CPU -- which matters on a
 battery-powered laptop -- to do *nothing*.

 Perhaps this is just a bad Java implementation, but perhaps there's
 something in the Cyberduck application which can be fixed.

--

Comment(by dkocher):

 I can't really explain this. One possible cause could be
 Rendezvous/Bonjour activity on the network (services appearing and
 disappearing). You could try if it makes a difference with Bonjour
 services discovery disabled for Cyberduck using

 {{{
 defaults write ch.sudo.cyberduck rendezvous.enable false
 }}}

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/3316#comment:1>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files and Amazon S3 Browser for Mac OS X.