184515 - mail uses 97% - 98% cpu, extensive disk activity, no swapping, to download mail

Status: RESOLVED DUPLICATE of bug 180516

(MailNews Core :: Networking: POP, defect)

Description

[David Lombard]

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

Downloading mail is consistently using 97-99% cpu accompanied by extensive disk
activity to download mail via a pop account.  850 MHz PIII, 512 MB memory; no
swapping;

NO issues were present w/ 1.1

Mail is unusable, must downgrade to 1.1

Reproducible: Always

Steps to Reproduce:
1.download mail from pop account.
2.
3.

Actual Results:  
mozilla froze for several minutes, extensive disk activity note, sluggish
response from rest of system, 99% cpu utilization by mozilla-bin.

Expected Results:  
been a good citizen

Comment 1

[Jo Hermans]

Already fixed on the trunk (bug 180516). Reporter, can you try a newer build ?

*** This bug has been marked as a duplicate of 180516 ***

Comment 2

[David Lombard]

I checked the dup, and the descriptions and traffic don't seem to point to the
same issues.

I am downloading mail, not sending it, and attachments are usually not present
in downloaded mail.  In messages where an attachment is present, the problem
might actually be worse, but the problem is present regardless of the presence
of an attachment to the email message (this is verified by watching the progress
indicators).

Reverting to 1.1 resolved the problem.

Comment 3

[esther]

David, your scenario refers to downloading pop msgs, the dup bug scenario was
senidng msg with large attachments.  This could possibly be related, if
possible,  please take the latest nightly build, try this again and report back
if it fixed your problem.  If it did not fix your problem, please give the build
identifier of the latest build and reopen this with a comment on your retest. Thanks

Comment 4

[esther]

David, fyi... another bug that was marked a dup of 180516 is 182080.  182080
scenario sounds more like your scenairo. 

Comment 5

[David Lombard]

Reading of bug 182080 does seem to show that the three bugs, 180516, 182080, and
184515 are all duplicates.