164404 - 100% load of CPU during mozilla's mail client starting

Status: RESOLVED FIXED

(MailNews Core :: Networking: IMAP, defect)

Description

[Arkady Sherman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020822
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020822

When i start mail client window with enabled chek IMAP server for new messages
at start up, that opens and does nothing for one or half minute, with CPU load
being 100%. And if i open any url at the same time in new window, it shows
"Resolving host for ..." until mail client goes to normal mode. 

Reproducible: Always

Steps to Reproduce:
1. -
2. -
3. -

Actual Results:  
-

Expected Results:  
-

Comment 1

[David :Bienvenu]

Is this new behaviour? can you attach an imap protocol log?

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 2

[Arkady Sherman]

Attachment: imap log file from the bug reporter

Comment 3

[Arkady Sherman]

Attachment: imap log file from the bug reporter

Comment 4

[Arkady Sherman]

Yes that is relatively new bug. There was no the bug at least in build 20020810...

And the IMAP log file seems to be clear during establishing the connection with
100% cpu usage.

Another comment: while loading any message the cpu usage is also 100%,even if
connection has been already established.

Comment 5

[Arkady Sherman]

This bug can be observed when i launch mail window first ("C:\Program
Files\mozilla.org\mozilla\mozilla.exe" -mail). There is no the bug when is
launch at first just brouser ("C:\Program Files\mozilla.org\mozilla\mozilla.exe").

Comment 6

[Arkady Sherman]

Excuse me for my importunity, but.
I've got dial-up connection to internet. Before this bug in older builds when i
launched mozilla mail and connection to internet had been broken, there was
immediately message - Failed to connect to server mail.ksu.ru. But now that is
only after some time (half minute), with cpu usage being 100% during this time.
My cpu is AthlonXP 1600+ ;-).

Comment 7

[David :Bienvenu]

taking, and fix upcoming.

Comment 8

[David :Bienvenu]

Attachment: proposed fix

If we didn't get any data from the stream, sleep for 50 milliseconds to avoid
hogging cpu - otherwise, hog away!

Comment 9

[(not reading, please use [e-mail] instead)]

Comment on attachment 96686 [details] [diff] [review]
proposed fix

sr=sspitzer

Comment 10

[David :Bienvenu]

This change makes it so if we didn't get any data from the stream, we sleep for
50 milliseconds before processing pending events. This makes us behave more or
less like we used to in the case where we haven't gotten any data, but should
still allow us to process data as quickly as possible when there is data. I
tried putting in a PR_Sleep(PR_INTERVAL_NO_WAIT) instead, but I still saw CPU
useage go up to 100% while waiting for data.

Comment 11

[Scott MacGregor]

Comment on attachment 96686 [details] [diff] [review]
proposed fix

r=mscott

I'll try it out on my opt. build later today but I didn't want to hold up the
train on this getting in.

Comment 12

[David :Bienvenu]

*** Bug 164632 has been marked as a duplicate of this bug. ***

Comment 13

[David :Bienvenu]

fix checked in.

Comment 14

[James Rome]

My bug 164632 is not during the IMAP startup. It is during the download of
attachments. 

Comment 15

[James Rome]

I will try tomorrow's build....

Comment 16

[David :Bienvenu]

no reason to re-open this bug.