Gaim 2.0 unusably slow in Edgy

This time should be roughly equivalent to the time you previously spent looking at the connection progress dialog. Is it longer with the betas, or are you primarily reacting to the lack of visual feedback?

The start time should also improve _at least_ some in beta4, but as I do not recall particularly long start times in beta3.1, I am unsure if that will fully address this bug.

thanks for responding. the time required to render the client, unfortunately, far exceeds the time required to connect.

in more detail: on relatively comparable hardware, using Dapper's GAIM, I can log into the exact same 4 accounts in just under 18 seconds.

on Edgy, as you can see from the attached screenshot - log in times to the GAIM client are exceeding 6 and a half minutes.

think i figured it out. after deactivating the "Evolution Integration" plugin, i can now login to my accounts on GAIM in under 20 seconds again - as opposed to 8+ minutes.

Interesting. Could you enable the plugin again and get a backtrace with GDB? Basically, you'd need to do something like this:

1. Start Gaim.
2. Find the PID of Gaim using ps (or whatever).

3. In a terminal, run:
  gdb
  attach Gaim_PID
  continue

4. Then, as Gaim is hanging, do this:
  Hit Ctrl-C
  bt full
  continue

5. Repeat step 4 several times, in sets of maybe 3 times, each separated by 1-2 seconds. So, you'd have something at like time T, T+1, T+2, T+30, T+30+1, T+30+2, T+60, T+60+1, T+60+2. That way, we might be able to figure out which code is executing while it hangs.

Post all the backtraces here, preferably each as separate attachments to make comparison easier.

well, the timing is all off b/c when it starts with the plugin enabled it's very resource hungry and locks things up regularly, but i've tried to get some backtraces for you.

if the time is the critical component here, i'll see what i can do.

meanwhile, these are in sequence of 1 (earliest) to 4 (latest).

debug trace 2

I have no clue what's going on here. I see AIM stuff in the backtraces, so maybe Mark has some idea...

don't know if it helps, but i've had issues with Evolution Data Server 1.8. it occasionally churns out of control, sucking up lots of cycles and memory and has to be killed.

Ekiga experiences similar startup issues, and i understand it's also integrated with EDS.

don't know if that's the problem, but thought it was worth passing along.

There IS a lot of oscar stuff in those backtraces... but since Gaim loads fine when the evolution plugin is not loaded, the oscar stuff is probably just a coincidence.

I'm don't really know what the next step would be in debugging this. I'm not familiar with Evolution or Gaim's Evolution plugin at all.

Should we forward this to the upstream bug tracker, so somebody else might have a look at it?

Do you still have this problem with Pidgin?

No, we can consider bug closed, although I no longer use the Evolution plugin which may or may not still be a problem.

So I'm closing this bug based on the last comment. If this bug still exists it should be reported again because the program isn't called Gaim anymore and the bug summary is misleading.