Presence of Kerberos tickets stalls Adium at launch

[apm_]

After upgrading to Lion, I noticed that Adium would seemingly stall for 20-30 seconds on launch; beach ball spins and buddy list window appears but is blank. I ignored this for a while figuring it was a Lion bug that would eventually be squished. After several months, and numerous betas, I started to muck around with Adium a little more and think I may have found the root cause: Kerberos tickets.

My organization uses Kerberos tickets for single sign-on. I have Lion configured to automatically grab me Kerberos tickets at login.

From pam.d:

Code: Select all

auth       optional       pam_krb5.so use_first_pass use_kcminit default_principal

When a valid Kerberos ticket is present, Adium writes these two entries to the Console:

Code: Select all

2/15/12 9:32:41.281 AM Adium: gss_init_sec_context is called on main thread, its a blocking api
2/15/12 9:32:41.283 AM Adium: krb5_sendto_context is called on main thread, its a blocking api

The first time Adium is started after a reboot -- meaning OS X has not stashed Adium assets in memory -- the program takes 20-40 seconds to launch. After this, quitting and relaunching speeds up; my assumption is that OS X is still holding Adium in memory and thus it starts quickly.

Any ideas?

Andrew

EDIT: Per the suggestion below, I've attached a process sample of Adium while the behavior is occurring.

[sphynx]

This appears to be the same as http://trac.adium.im/ticket/14091, however, it's a bit sparse. It could help tracking down the problem if you could create a sample of Adium while this is happening, instructions are here: http://trac.adium.im/wiki/Sampling.

[apm_]

Thanks, @sphynx. The two reports do seem to be related.

Per your suggestion, I've included a sample in the original post.

APM