[Cyberduck-trac] [Cyberduck] #8115: [Cyberduck] #8101: Hangs on start (was: Cyberduck hangs on start)

Cyberduck trac at trac.cyberduck.io
Sat Jul 26 13:23:00 UTC 2014


#8115: [Cyberduck] #8101: Hangs on start (was: Cyberduck hangs on start)
---------------------------+-------------------------
 Reporter:  Gscot          |         Owner:  dkocher
     Type:  defect         |        Status:  assigned
 Priority:  normal         |     Milestone:
Component:  core           |       Version:  4.5
 Severity:  normal         |    Resolution:
 Keywords:                 |  Architecture:  Intel
 Platform:  Mac OS X 10.9  |
---------------------------+-------------------------
Changes (by dkocher):

 * owner:   => dkocher
 * status:  new => assigned


Old description:

> I find no ticket available for the continuation of this issue. I
> attempted to respond to aid on this topic, but it was to a "noreply"
> address.  Finding no other logical way I'll put that continuing
> correspondence here.
>
> On Jul 25, 2014, at 5:26 AM, Cyberduck <trac at trac.cyberduck.io> wrote:
>
> #8101: Hangs on start
> --------------------+--------------------
> Reporter:  Gscot   |         Owner:
>     Type:  defect  |        Status:  new
> Priority:  normal  |     Milestone:
> Component:  core    |       Version:  4.5
> Severity:  normal  |    Resolution:
> Keywords:          |  Architecture:
> Platform:          |
> --------------------+--------------------
>
> Comment (by dkocher):
>
> Please update to the latest
> [http://trac.cyberduck.ch/wiki/help/en/faq#SnapshotandBetabuilds
> snapshot]
> build available and report back if the problem persists.
>
> Done.  The problem persists.
>
> Please include
> the file `cyberduck.log` in the
> [http://trac.cyberduck.ch/wiki/help/en/faq#Wherearepreferencesandapplicationsettingssavedto
> application support directory].
>
> Looking at this Faq page the indication is that the cyberduck.log file is
> stored in the appdata directory and the appdata directory is peculiar to
> the Windows version of this program. I am using the Mac version of the
> program.
>
> Looking in the console, a program with which I am only marginally
> operational, I see this under “all messages” (.png screen capture):
>
>      http://grab.by/yTSK
>
> In the system log there is this:
>
> Jul 25 08:41:28 Ducks.local WindowServer[168]: disable_update_timeout: UI
> updates were forcibly disabled by application "Cyberduck" for over 1.00
> seconds. Server has re-enabled them.
> Jul 25 08:41:29 Ducks.local WindowServer[168]: common_reenable_update: UI
> updates were finally reenabled by application "Cyberduck" after 2.01
> seconds (server forcibly re-enabled them after 1.00 seconds)
> Jul 25 08:41:29 Ducks.local Cyberduck[664]: [background-3] FATAL
> ch.cyberduck.ui.AbstractController - Unhandled exception running
> background task null
>                 at ch.cyberduck.core.Host.serialize(Host.java:360)
>                 at
> ch.cyberduck.core.serializer.impl.PlistWriter.write(PlistWriter.java:79)
>                 at
> ch.cyberduck.core.AbstractFolderHostCollection.collectionItemAdded(AbstractFolderHostCollection.java:71)
>                 at
> ch.cyberduck.core.AbstractFolderHostCollection.collectionItemAdded(AbstractFolderHostCollection.java:31)
>                 at ch.cyberduck.core.Collection.add(Collection.java:108)
>                 at
> ch.cyberduck.core.AbstractHostCollection.add(AbstractHostCollection.java:96)
>                 at
> ch.cyberduck.core.HistoryCollection.add(HistoryCollection.java:90)
>                 at
> ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:112)
>                 at
> ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:947)
>                 at
> ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:944)
>                 at
> ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
>                 at
> ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:159)
>                 at
> ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
> Jul 25 08:41:29 Ducks.local Cyberduck[664]: Performance: Please update
> this scripting addition to supply a value for ThreadSafe for each event
> handler: "/Library/ScriptingAdditions/SIMBL.osax"
> Jul 25 08:41:30 Ducks kernel[0]: Cyberduck (map: 0xffffff8049d1ef00)
> triggered DYLD shared region unnest for map: 0xffffff8049d1ef00, region
> 0x7fff8c000000->0x7fff8c200000. While not abnormal for debuggers, this
> increases system memory footprint until the target exits.
> Jul 25 08:41:35 Ducks.local Cyberduck[664]: [main] ERROR
> org.rococoa.callback - Exception calling method for selector
> setProtocolCombobox:
>                 at
> ch.cyberduck.ui.cocoa.foundation.NSBundle.loadNibNamed(NSBundle.java:47)
>                 at
> ch.cyberduck.ui.cocoa.BundleController.loadBundle(BundleController.java:74)
>                 at
> ch.cyberduck.ui.cocoa.BundleController.loadBundle(BundleController.java:62)
>                 at
> ch.cyberduck.ui.cocoa.PreferencesController.<init>(PreferencesController.java:81)
>                 at
> ch.cyberduck.ui.cocoa.PreferencesControllerFactory$1.<init>(PreferencesControllerFactory.java:36)
>                 at
> ch.cyberduck.ui.cocoa.PreferencesControllerFactory.instance(PreferencesControllerFactory.java:36)
>                 at
> ch.cyberduck.ui.cocoa.MainController.preferencesMenuClicked(MainController.java:497)
>                 at
> ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
>                 at
> ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:146)
>                 at
> ch.cyberduck.ui.cocoa.PreferencesController.setProtocolCombobox(PreferencesController.java:1635)
> Jul 25 08:41:43 Ducks.local Cyberduck[664]: [main] ERROR
> org.rococoa.callback - Exception calling method for selector
> menu:updateItem:atIndex:shouldCancel:
>                 at
> ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
>                 at
> ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:146)
>                 at
> ch.cyberduck.ui.cocoa.delegate.HistoryMenuDelegate.menuUpdateItemAtIndex(HistoryMenuDelegate.java:107)
>                 at
> ch.cyberduck.ui.cocoa.delegate.AbstractMenuDelegate.menu_updateItem_atIndex_shouldCancel(AbstractMenuDelegate.java:53)
> Jul 25 08:41:50 Ducks.local Cyberduck[664]: 10.4-style NSDateFormatter
> method called on a 10.0-style formatter, which doesn't work. Break on
> _NSDateFormatter_Log_New_Methods_On_Old_Formatters to debug. This message
> will only be logged once.
> Jul 25 08:43:26 Ducks.local launchservicesd[57]: Application
> App:"Cyberduck" asn:0x0-54054 pid:664 refs=7 @ 0x7f95bc927f60 tried to be
> brought forward, but isn't in fPermittedFrontApps ( (
> "LSApplication:0x0-0x57057 pid=689 "SecurityAgent"")), so denying. :
> LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5
> queue
> Jul 25 08:43:26 Ducks.local WindowServer[168]: [cps/setfront] Failed
> setting the front application to Cyberduck, psn 0x0-0x54054,
> securitySessionID=0x186a5, err=-13066
> Jul 25 08:43:32 Ducks.local WindowServer[168]: disable_update_timeout: UI
> updates were forcibly disabled by application "Cyberduck" for over 1.00
> seconds. Server has re-enabled them.
> Jul 25 08:43:32 Ducks.local WindowServer[168]: common_reenable_update: UI
> updates were finally reenabled by application "Cyberduck" after 1.22
> seconds (server forcibly re-enabled them after 1.00 seconds)
> Jul 25 08:43:32 Ducks.local Cyberduck[699]: [background-2] FATAL
> ch.cyberduck.ui.AbstractController - Unhandled exception running
> background task null
>                 at ch.cyberduck.core.Host.<init>(Host.java:158)
>                 at ch.cyberduck.core.Host.<init>(Host.java:132)
>                 at
> ch.cyberduck.core.serializer.HostDictionary.deserialize(HostDictionary.java:46)
>                 at
> ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:45)
>                 at
> ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:30)
>                 at
> ch.cyberduck.core.serializer.impl.PlistReader.read(PlistReader.java:72)
>                 at
> ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:128)
>                 at
> ch.cyberduck.core.BookmarkCollection.load(BookmarkCollection.java:248)
>                 at
> ch.cyberduck.ui.cocoa.MainController$12.run(MainController.java:952)
>                 at
> ch.cyberduck.ui.cocoa.MainController$12.run(MainController.java:948)
>                 at
> ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
>                 at
> ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:165)
>                 at
> ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
> Jul 25 08:43:32 Ducks.local Cyberduck[699]: [background-3] FATAL
> ch.cyberduck.ui.AbstractController - Unhandled exception running
> background task null
>                 at ch.cyberduck.core.Host.<init>(Host.java:158)
>                 at ch.cyberduck.core.Host.<init>(Host.java:132)
>                 at
> ch.cyberduck.core.serializer.HostDictionary.deserialize(HostDictionary.java:46)
>                 at
> ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:45)
>                 at
> ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:30)
>                 at
> ch.cyberduck.core.serializer.impl.PlistReader.read(PlistReader.java:72)
>                 at
> ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:128)
>                 at
> ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:976)
>                 at
> ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:973)
>                 at
> ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
>                 at
> ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:165)
>                 at
> ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
> Jul 25 08:43:32 Ducks.local Cyberduck[699]: Performance: Please update
> this scripting addition to supply a value for ThreadSafe for each event
> handler: "/Library/ScriptingAdditions/SIMBL.osax"
> Jul 25 08:43:33 Ducks kernel[0]: Cyberduck (map: 0xffffff80420b63c0)
> triggered DYLD shared region unnest for map: 0xffffff80420b63c0, region
> 0x7fff8c000000->0x7fff8c200000. While not abnormal for debuggers, this
> increases system memory footprint until the target exits.
> Jul 25 08:44:07 Ducks.local KeyCue[399]: *** process changed (B) from
> Process "DEVONthink Pro" (DNtp) 2.7.6 to Process "Cyberduck" (CYCK) 4.4.3
> Jul 25 08:44:07 Ducks.local KeyCue[399]: *** process changed (A) from
> Process "DEVONthink Pro" (DNtp) 2.7.6 to Process "Cyberduck" (CYCK) 4.4.3
>
> There is nothing in View > toggle Log drawer.  The Cyberduck window
> continues to look like this throughout:
>
>      http://grab.by/yTTA

New description:

 I find no ticket available for the continuation of this issue. I attempted
 to respond to aid on this topic, but it was to a "noreply" address.
 Finding no other logical way I'll put that continuing correspondence here.

 On Jul 25, 2014, at 5:26 AM, Cyberduck <trac at trac.cyberduck.io> wrote:

 > Please update to the latest
 > [http://trac.cyberduck.ch/wiki/help/en/faq#SnapshotandBetabuilds
 snapshot]
 > build available and report back if the problem persists.

 Done.  The problem persists.

 > Please include
 > the file `cyberduck.log` in the
 >
 [http://trac.cyberduck.ch/wiki/help/en/faq#Wherearepreferencesandapplicationsettingssavedto
 > application support directory].

 Looking at this Faq page the indication is that the cyberduck.log file is
 stored in the appdata directory and the appdata directory is peculiar to
 the Windows version of this program. I am using the Mac version of the
 program.

 Looking in the console, a program with which I am only marginally
 operational, I see this under “all messages” (.png screen capture):

      http://grab.by/yTSK

 In the system log there is this:


 {{{
 Jul 25 08:41:28 Ducks.local WindowServer[168]: disable_update_timeout: UI
 updates were forcibly disabled by application "Cyberduck" for over 1.00
 seconds. Server has re-enabled them.
 Jul 25 08:41:29 Ducks.local WindowServer[168]: common_reenable_update: UI
 updates were finally reenabled by application "Cyberduck" after 2.01
 seconds (server forcibly re-enabled them after 1.00 seconds)
 Jul 25 08:41:29 Ducks.local Cyberduck[664]: [background-3] FATAL
 ch.cyberduck.ui.AbstractController - Unhandled exception running
 background task null
                 at ch.cyberduck.core.Host.serialize(Host.java:360)
                 at
 ch.cyberduck.core.serializer.impl.PlistWriter.write(PlistWriter.java:79)
                 at
 ch.cyberduck.core.AbstractFolderHostCollection.collectionItemAdded(AbstractFolderHostCollection.java:71)
                 at
 ch.cyberduck.core.AbstractFolderHostCollection.collectionItemAdded(AbstractFolderHostCollection.java:31)
                 at ch.cyberduck.core.Collection.add(Collection.java:108)
                 at
 ch.cyberduck.core.AbstractHostCollection.add(AbstractHostCollection.java:96)
                 at
 ch.cyberduck.core.HistoryCollection.add(HistoryCollection.java:90)
                 at
 ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:112)
                 at
 ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:947)
                 at
 ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:944)
                 at
 ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
                 at
 ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:159)
                 at
 ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
 Jul 25 08:41:29 Ducks.local Cyberduck[664]: Performance: Please update
 this scripting addition to supply a value for ThreadSafe for each event
 handler: "/Library/ScriptingAdditions/SIMBL.osax"
 Jul 25 08:41:30 Ducks kernel[0]: Cyberduck (map: 0xffffff8049d1ef00)
 triggered DYLD shared region unnest for map: 0xffffff8049d1ef00, region
 0x7fff8c000000->0x7fff8c200000. While not abnormal for debuggers, this
 increases system memory footprint until the target exits.
 Jul 25 08:41:35 Ducks.local Cyberduck[664]: [main] ERROR
 org.rococoa.callback - Exception calling method for selector
 setProtocolCombobox:
                 at
 ch.cyberduck.ui.cocoa.foundation.NSBundle.loadNibNamed(NSBundle.java:47)
                 at
 ch.cyberduck.ui.cocoa.BundleController.loadBundle(BundleController.java:74)
                 at
 ch.cyberduck.ui.cocoa.BundleController.loadBundle(BundleController.java:62)
                 at
 ch.cyberduck.ui.cocoa.PreferencesController.<init>(PreferencesController.java:81)
                 at
 ch.cyberduck.ui.cocoa.PreferencesControllerFactory$1.<init>(PreferencesControllerFactory.java:36)
                 at
 ch.cyberduck.ui.cocoa.PreferencesControllerFactory.instance(PreferencesControllerFactory.java:36)
                 at
 ch.cyberduck.ui.cocoa.MainController.preferencesMenuClicked(MainController.java:497)
                 at
 ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
                 at
 ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:146)
                 at
 ch.cyberduck.ui.cocoa.PreferencesController.setProtocolCombobox(PreferencesController.java:1635)
 Jul 25 08:41:43 Ducks.local Cyberduck[664]: [main] ERROR
 org.rococoa.callback - Exception calling method for selector
 menu:updateItem:atIndex:shouldCancel:
                 at
 ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
                 at
 ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:146)
                 at
 ch.cyberduck.ui.cocoa.delegate.HistoryMenuDelegate.menuUpdateItemAtIndex(HistoryMenuDelegate.java:107)
                 at
 ch.cyberduck.ui.cocoa.delegate.AbstractMenuDelegate.menu_updateItem_atIndex_shouldCancel(AbstractMenuDelegate.java:53)
 Jul 25 08:41:50 Ducks.local Cyberduck[664]: 10.4-style NSDateFormatter
 method called on a 10.0-style formatter, which doesn't work. Break on
 _NSDateFormatter_Log_New_Methods_On_Old_Formatters to debug. This message
 will only be logged once.
 Jul 25 08:43:26 Ducks.local launchservicesd[57]: Application
 App:"Cyberduck" asn:0x0-54054 pid:664 refs=7 @ 0x7f95bc927f60 tried to be
 brought forward, but isn't in fPermittedFrontApps ( (
 "LSApplication:0x0-0x57057 pid=689 "SecurityAgent"")), so denying. :
 LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
 Jul 25 08:43:26 Ducks.local WindowServer[168]: [cps/setfront] Failed
 setting the front application to Cyberduck, psn 0x0-0x54054,
 securitySessionID=0x186a5, err=-13066
 Jul 25 08:43:32 Ducks.local WindowServer[168]: disable_update_timeout: UI
 updates were forcibly disabled by application "Cyberduck" for over 1.00
 seconds. Server has re-enabled them.
 Jul 25 08:43:32 Ducks.local WindowServer[168]: common_reenable_update: UI
 updates were finally reenabled by application "Cyberduck" after 1.22
 seconds (server forcibly re-enabled them after 1.00 seconds)
 Jul 25 08:43:32 Ducks.local Cyberduck[699]: [background-2] FATAL
 ch.cyberduck.ui.AbstractController - Unhandled exception running
 background task null
                 at ch.cyberduck.core.Host.<init>(Host.java:158)
                 at ch.cyberduck.core.Host.<init>(Host.java:132)
                 at
 ch.cyberduck.core.serializer.HostDictionary.deserialize(HostDictionary.java:46)
                 at
 ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:45)
                 at
 ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:30)
                 at
 ch.cyberduck.core.serializer.impl.PlistReader.read(PlistReader.java:72)
                 at
 ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:128)
                 at
 ch.cyberduck.core.BookmarkCollection.load(BookmarkCollection.java:248)
                 at
 ch.cyberduck.ui.cocoa.MainController$12.run(MainController.java:952)
                 at
 ch.cyberduck.ui.cocoa.MainController$12.run(MainController.java:948)
                 at
 ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
                 at
 ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:165)
                 at
 ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
 Jul 25 08:43:32 Ducks.local Cyberduck[699]: [background-3] FATAL
 ch.cyberduck.ui.AbstractController - Unhandled exception running
 background task null
                 at ch.cyberduck.core.Host.<init>(Host.java:158)
                 at ch.cyberduck.core.Host.<init>(Host.java:132)
                 at
 ch.cyberduck.core.serializer.HostDictionary.deserialize(HostDictionary.java:46)
                 at
 ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:45)
                 at
 ch.cyberduck.core.serializer.impl.HostPlistReader.deserialize(HostPlistReader.java:30)
                 at
 ch.cyberduck.core.serializer.impl.PlistReader.read(PlistReader.java:72)
                 at
 ch.cyberduck.core.AbstractFolderHostCollection.load(AbstractFolderHostCollection.java:128)
                 at
 ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:976)
                 at
 ch.cyberduck.ui.cocoa.MainController$13.run(MainController.java:973)
                 at
 ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
                 at
 ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:165)
                 at
 ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
 Jul 25 08:43:32 Ducks.local Cyberduck[699]: Performance: Please update
 this scripting addition to supply a value for ThreadSafe for each event
 handler: "/Library/ScriptingAdditions/SIMBL.osax"
 Jul 25 08:43:33 Ducks kernel[0]: Cyberduck (map: 0xffffff80420b63c0)
 triggered DYLD shared region unnest for map: 0xffffff80420b63c0, region
 0x7fff8c000000->0x7fff8c200000. While not abnormal for debuggers, this
 increases system memory footprint until the target exits.
 Jul 25 08:44:07 Ducks.local KeyCue[399]: *** process changed (B) from
 Process "DEVONthink Pro" (DNtp) 2.7.6 to Process "Cyberduck" (CYCK) 4.4.3
 Jul 25 08:44:07 Ducks.local KeyCue[399]: *** process changed (A) from
 Process "DEVONthink Pro" (DNtp) 2.7.6 to Process "Cyberduck" (CYCK) 4.4.3
 }}}


 There is nothing in View > toggle Log drawer.  The Cyberduck window
 continues to look like this throughout:

      http://grab.by/yTTA

--

Comment:

 [[Image(http://new.tinygrab.com/64fdc1957955b379f97d4e57df4d311056e6b39ee6.png)]]

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


More information about the Cyberduck-trac mailing list