Closed Bug 278882 Opened 20 years ago Closed 20 years ago

junk filter causes Mozilla to use 100% CPU

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: doeni.bug, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050111
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050111

Since 20050116 when starting up Mozilla mail, the CPU usage goes up to 100% when
the junk filter marks new mails as Junk.
Mozilla mail worked fine until 20050111. So problem must have started to appear
between those 2 builds.

I tried deleting the training.dat, and initially the problem did not reproduce.
However after marking a few messages as junk, the problem reproduced.

Mails are stored on POP3 server.

Reproducible: Always

Steps to Reproduce:
1. Startup mozilla mail (junk filter must be enabled)
2. Let mozilla mark new mails as Junk, or manually mark some mails as junk

Actual Results:  
Notice Mozilla using 100% CPU


Expected Results:  
normal CPU usage

Build arguments :
--enable-application=suite --enable-default-toolkit=gtk2 --enable-calendar
--enable-xft --disable-postscript --disable-xprint --enable-crypto
--disable-installer --disable-debug --enable-optimize=-O3

The same arguments were used to build the working mozilla mail application.

Bug looks similar to bug 262743, but deleting training.dat does not solve the
issue here.
Version: unspecified → Trunk
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8b2) Gecko/20050318

I can't reproduce this.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8b2) Gecko/20050318

I can't reproduce this under Windows 2000, just for reference.
I'm unable to reproduce the issue in the latest builds.
Assignee: sspitzer → mail
Based on report's new findings, closing bug.  Resolution == WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.