From: Tim Hentenaar <tth@on...> - 2004-06-15 12:44:44
I'm working on a protocol plugin, and it's coming along nicely, though I've run into a major problem. After the login process is finalized, gaim displays the buddy list, etc. as usual, but within a few seconds, it starts raping my cpu. (Just after the last packet of the login sequence is received, and about 5 - 6 seconds after calling gaim_connection_set_state().)
It's not too easy to pinpoint the problem, and I was wondering if any of you all have any ideas as to what could be causing it. The only think I can think that would cause it would be if the read callback were continuously being hit, but that shouldn't happen, and even so, it would return soon after it were called.
Any help would be appreciated. :P
Get latest updates about Open Source Projects, Conferences and News.