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



12 years ago
10 years ago


(Reporter: bugs, Assigned: mscott)


Windows XP

Firefox Tracking Flags

(Not tracked)




12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20061204 Firefox/
Build Identifier: Version (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

12 years ago
Is this something that started recently? Does it happen with a 2.0 beta?
Version: unspecified → 1.5

Comment 2

12 years ago
(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

12 years ago
related to bug 363163 ???
I'm inclined to dupe this to some of the recent perf bugs about resources being eaten up continuously, thoughts?

Comment 5

10 years ago
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

10 years ago
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
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.