124872 - Compose window: Hung while typing away.

Status: VERIFIED DUPLICATE of bug 124209

(MailNews Core :: Composition, defect)

Description

[Cavin Song]

BuildID: 20020207; winNT

I have been getting this a lot lately (for the past two plus weeks) and this 
morning it happened to me again.  I played with it a few times and I could 
reproduce it 80% of the tries using the following steps:

1. Launch a compose window.
2. Type something in the address field (like, 'tim') in the address field and 
select the right recipient from the list.
3. Tab to the Subject field and enter something there.
4. Tab into the body and start typing. You should have at least one paragraph in 
the body so it looks something like:

   Tim,

   This is a test. This is a test. . . .
   This is a test1. This is a test1.

5. Then (this is the key), at the end of the 1st paragraph hit the 'Enter' key 
twice very quickly (so you can start typing the 2nd paragraph).

At this point the program hung and the Task Manager showed the 100% CPU time 
occupied by the mailnews program. I was able to make it happen a few times.

Not sure if this is a regression but I don't recall I even ran into this problem 
before.

Comment 1

[Cavin Song]

I just did it again and I think step #5 should be changed to the following:

5. Then (this is the key), at the end of the 1st paragraph hit the 'Enter' key 
twice very quickly (so you can start typing the 2nd paragraph) and start typing 
away.  Don't stop typing after you've hit 'Enter' twice.

This time, before it hung it showed the first char I typed (ie, 'C') in the 
compose window. In other words, I typed 'Enter', 'Enter' and 'Cavin' very 
quickly and it showed a newline and 'C' before hanging.

Comment 2

[Cavin Song]

One more note, it does not matter if this is a new compose or not becuse last 
time it happened I launced it from the Drafts folder (since I kept losing the 
msg text so I saved it to Drafts).

Comment 3

[Jean-Francois Ducarroz]

Caving, please try a recent build. Kin should have already fixed this problem...

Comment 4

[laurel]

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

Comment 5

[laurel]

marking verified as a duplicate