@dkocher commented

Plus attach the file cyberduck.log in the application support directory.

f411c1e commented

Ok, David, log added, thanks...

@dkocher commented

2014-06-29 23:33:21,080 [background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
java.lang.ArrayIndexOutOfBoundsException
	at cli.System.Collections.Generic.Dictionary$$00602.Insert(Unknown Source)
	at cli.System.Collections.Generic.Dictionary$$00602.set_Item(Unknown Source)
	at cli.Ch.Cyberduck.Core.I18n.LocaleImpl.ReadBundleIntoCache(Unknown Source)
	at cli.Ch.Cyberduck.Core.I18n.LocaleImpl.localize(Unknown Source)
	at ch.cyberduck.core.LocaleFactory.localizedString(LocaleFactory.java:72)
	at ch.cyberduck.ui.action.MountWorker.getActivity(MountWorker.java:80)
	at ch.cyberduck.ui.threading.WorkerBackgroundAction.getActivity(WorkerBackgroundAction.java:84)
	at ch.cyberduck.core.threading.SessionBackgroundAction.prepare(SessionBackgroundAction.java:121)
	at ch.cyberduck.ui.threading.ControllerBackgroundAction.prepare(ControllerBackgroundAction.java:52)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:163)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
	at java.lang.Thread.run(Thread.java:937)

@dkocher commented

In what language do you run Cyberduck? It looks like there is an error with a localizable resource bundle.

f411c1e commented

In English - presumably en_us, as it's on Windows 8.1.

Interesting that this may turn out to have to do with Locales...

@ylangisc commented

In f437ae5.

@dkocher commented

Can you please confirm this issue is fixed by updating to the latest beta build available.

f411c1e commented

Hallo David,
Yes, this issue appears fixed. I tried it as soon as the update appeared, but wanted to try it again, and did today on receipt of your note. No such problem observed now, so thank you on that; I think you and your team got it.

There is one other problem I saw, just after installation. I ran Cyberduck, no problem, closed it, and tried to run again. No Cyberduck appeared, so thinking I'd missed clicking the icon, I tried again. Still no result, so I looked at the Task Manager and found two Cyberducks running silently in the background.

Mysteriously, I couldn't succeed at End Task on either of these in any usual way - this was a hard block, tempting to thing that Cyberduck was lost somewhere in a driver.

I waited, perhaps a minute, and then both unruly Cyberducks self-closed. After this, I could start and stop them very rapidly, without any ghost processes or duplicate executions.

I'm enclosing the log afresh, in hopes you might find something there. I had a feeling this occurred perhaps due to just running the updater, but it's only a feeling, and with some basis in that the problem went away once we moved away from that time period.

Regards,
Clive