Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Taking a long time before actual application launch #5685

Closed
cyberduck opened this issue Feb 2, 2011 · 7 comments
Closed

Taking a long time before actual application launch #5685

cyberduck opened this issue Feb 2, 2011 · 7 comments
Labels
bug core thirdparty

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 2, 2011

0f75e4b created the issue

Since updating my MacBook Pro to 10.6.6, Cyberduck takes a few minutes to open, during which time Activity Monitor shows a high CPU load.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

@dkocher commented

Please enable debug logging and send me any related output in system.log (/Applications/Utilities/Console.app) after launching the application.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

0f75e4b commented

log attached

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

@dkocher commented

The log only shows 5 seconds for application startup including loading the bookmarks and history. Confused.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

0f75e4b commented

Yes I know. The logs only populated when the app window appeared. It was a full minute before this when the dock icon was clicked.

This behaviour has only started since 10.6.6 was installed.

Even more confused.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

@dkocher commented

Any content before that in the log?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2011

0f75e4b commented

The only entry in the log, prior to the launch of Cyberduck is;

Feb  3 10:14:02 MacBook-Pro-2 com.apple.launchd[1] (com.themha.airlock.daemon[1946]): getpwnam("_airlock_daemon") failed
Feb  3 10:14:02 MacBook-Pro-2 com.apple.launchd[1] (com.themha.airlock.daemon[1946]): Exited with exit code: 1
Feb  3 10:14:02 MacBook-Pro-2 com.apple.launchd[1] (com.themha.airlock.daemon): Throttling respawn: Will start in 10

Which I have since dealt with (stopped with terminal). Cyberduck still takes a long time to launch though.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 14, 2011

@dkocher commented

Try to create another test user account on the computer and see if there is any difference when launching the application from there.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug core thirdparty
Projects
None yet
Development

No branches or pull requests

1 participant