Cyberduck
Mountain Duck
CLI#3316 closed enhancement (worksforme)
Excess CPU use when application should be completely idle
| Reported by: | Mly@… | Owned by: | dkocher |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | core | Version: | 3.2 |
| Severity: | normal | Keywords: | |
| Cc: | Architecture: | ||
| Platform: |
Description (last modified by dkocher)
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.
Attachments (1)
Change History (4)
Changed on Jul 11, 2009 at 6:37:41 PM by Mly@…
comment:1 Changed on Jul 11, 2009 at 7:18:55 PM by dkocher
- Description modified (diff)
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
comment:2 Changed on Jul 11, 2009 at 7:42:54 PM by anonymous
Thanks for the quick suggestion. I've added that preference and I'll report back if I still see idle application CPU cycle consumption
comment:3 Changed on Nov 13, 2009 at 11:22:14 PM by dkocher
- Resolution set to worksforme
- Status changed from new to closed
Activity Monitor.app process sample