100% CPU utilizatioin after multiple IMAP errors

[Q]

Binary package hint: mozilla-thunderbird

Whenever my mail server sends an unexpected error, I get 100% cpu usage in Thunderbird until I dismiss the error dialog. The text of the dialog is "mail.blah.blah has sent an incorrect or unexpected message. Error Code: -12263". I realize my isp's imap mail server very likely has some issues, but Thunderbird shouldn't peg the cpu until an error dialog is dismissed.

I see this problem almost daily. I'll often have several of the dialogs stacked (I have multiple imap accounts). This has been happening since at least Edgy and still happens in Hardy.

Required info:
 Description: Ubuntu 8.04.1
 Release: 8.04

 mozilla-thunderbird:
  Installed: 2.0.0.16+nobinonly-0ubuntu0.8.04.1
  Candidate: 2.0.0.16+nobinonly-0ubuntu0.8.04.1
  Version table:
 *** 2.0.0.16+nobinonly-0ubuntu0.8.04.1 0
        500 http://us.archive.ubuntu.com hardy-updates/main Packages
        500 http://security.ubuntu.com hardy-security/main Packages
        100 /var/lib/dpkg/status
     2.0.0.12+nobinonly-0ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages

Expected Result:
 CPU should not be pegged when an error dialog.

Actual Result:
 When an error is encountered with an imap server, the cpu is pegged while the error dialog is displayed.

[Q (qucae19)]

One additional comment. When I only have one such error, the cpu normally does not peg. It's when all four accounts have stacked errors does the cpu peg. Only one error dialog shows at a time. Once you dismiss the first, the next pops up.

[Joel Goguen (jgoguen)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Joel Goguen (jgoguen)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Przemek K. (azrael)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!