I'm using a new svn version of Adium nearly everyday. But since quite some time (I think three or four days) everytime I wake up my Mac from sleep Adium uses up to 150% CPU power and doesn't stop with it until I quit it. It doesn't matter if compiled using Development oder Deployment. I would go back to the actual 1.1.2 but I love the message counter in the menubar so I don't want to miss it.
This bug is reproducable on my Macbook Core Duo 2.0 GHz with all the latest updates from Apple everytime after waking up from sleep. So I think it has something to to with the way Adium is reacting when the OS goes to sleep what results in this behaviour on waking up. This is just a guess since I'm not a programmer. But to me this looks logical. Correct me if I'm wrong.
Okay, I know you don't prefer getting code samples here. But I'm too lazy at the moment to register at the trac. Sorry for that. Next time I'll be more friendly. Here's what the sample looks like after waking up which still causes Adium having high CPU usage.
Okay... Here's another thing I just realized. Seems to have nothing to do with the sleep mode. It must have to do something with reconnecting. I tried it (reproducable) this way: Login to all accounts (ICQ, AIM, Y!, MSN, Google Talk, Bonjour) then disconnect from internet (unplug the ethernet cable). Then plug the cable back in. After (or while) all accounts log on again the CPU usage raises up to 175% and just quitting Adium stops the fan from spinning like crazy.
Maybe this helps a bit more and hopefully you can reproduce it.
And once again me. Sorry guys! But after some further investigation I think this problem has something to do with the way Adium tries to reconnect after the connection got lost.
I opened my Activity Monitor and unplugged my ethernet cable. As soon as I do that the CPU usage raises. It suddenly stops when I switch into offline status on all accounts. When I plug the cable back in and reconnect after that, Adium just connects as expected. I Hope this is helpful in any way.
The used build was 1.2svn r20979 built with Xcode configuration Development. I'm running Adium on a MacBook Core Duo 2.0 GHz with Mac OS X 10.4.10 and all actual updates (Software Update doesn't show anything new) and I have installed Safari 3.0.3 beta. But the problem was also present with the latest Safari 2.
This looks like a symptom of http://trac.adiumx.com/ticket/7887 -- if you `svn up` it'll probably handle it nicer (it won't be printing the same lines over and over and over), but it's still broken on network availability loss. Also check your console.log in /Library/Logs/Console -- it's probably very big.