365177 - TB continuously eats up CPU resources; UI does not respond while doing so

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[bogomip]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Version 1.5.0.9 (20061207)

TB manages 10 POP3 accounts with roughly 300000 Mails in about 50 different folders (the biggest with about 100000 mails). The polling intervals are distinct prime numbers. Downloaded mails are not being deleted on the server.

TB claims 100% of a CPU-core triggered by minimal user interaction (e.g. clicking in the folder tree) and/or probably timer events. If this occurs the UI does not respond and one has to wait several seconds until the next key stroke or mouse click is accepted.

Stat: TB consumed 1:45 hours CPU time within 12:30 hours system uptime.

Reproducible: Always

Steps to Reproduce:
1. Have many mails.

Comment 1

[Magnus Melin [:mkmelin]]

Is this something that started recently? Does it happen with a 2.0 beta?
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8/

Comment 2

[bogomip]

(In reply to comment #1)
> Is this something that started recently?

Recently I've migrated some mailboxes to TB. So I don't know if earlier versions had the same problem.

> Does it happen with a 2.0 beta?

TB version 2 beta 1 (20061201) has the same problem. Additionally the memory consumption is about 250 MB.

Comment 3

[Jean-Michel Reghem]

related to bug 363163 ???

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

I'm inclined to dupe this to some of the recent perf bugs about resources being eaten up continuously, thoughts?

Comment 5

[Wayne Mery (:wsmwk)]

depends on the bug :) i.e. how "likely" the bug is to really be a dupe.
is there a bug statistician in the house?  :)

and what's that talk about prime numbers in comment 0 all about?  spooky!

Comment 6

[Wayne Mery (:wsmwk)]

bogomip, if you still see this problem please comment.
=> incomplete - pinged 2007-05-08, no response, not enough symptoms to pin clearly to a specific dupe