From time to time Twitmonger maxes out on CPU usage. This is a bug inherited from Qwitter, possibly introduced during the v5 beta cycle (but I'm not absolutely sure).
It's happening on two Windows 7 desktop machines (one 32bit and one 64bit). When it happens I need to reboot in order to get everything running normally again.
There doesn't seem to be a consistent action that causes it. It's happened whilst browsing buffers, moving between buffers, and when editing tweets.
It doesn't seem to happen on my laptop (also Win7 64bit), which suggests there might be a time factor involved. This is highly speculative though.
Applications likely to be running on the machine when this happens: Jaws (12 or 13), Outlook 2003 and Firefox.