215725 - Reading Mail Messages causes occasional total lockup of computer

Status: RESOLVED DUPLICATE of bug 212240

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Jeff Sumberg]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718

This problem was reported in version 1.4 in bug #212240. I experienced the
problem so bad that the lockup occured every two or three read messages. When
the computer was rebooted, it would only take a few more reads to get it to
happed again. It was so bad, I had to back up to a prior version. I thien tried
1.5 Aplha, and the problem is still there, but not as bad. Now the lockup occurs
every other day or so, but it's still the same problem. As soon as you click a
header, the cursor goes "busy" (hourglass with arrow), but the message never
appears in the preview pane. At the point the machine is locked up. When I say
locked up I mean the Windows UI is locked. Jobs running in the background seem
to continue to run, but you cannot change windows, you cannot bring up the task
manager. For all purposes, the OS is dead. The only way to restart is a hard
reset (Ctrl-Alt-Del does not work). If you had any other programs running with
open files, you've lost that data because you must reset.

Reproducible: Sometimes

Steps to Reproduce:
1. Just read mail. Eventually it locks up. Nothing is special about the messages.
2. Problem more apparent in version 1.4 where every 3-5 messages read it locks up.
3. Doesn't matter if Mozilla is only program running or with many others.

Actual Results:  
Cursor shows busy w/ arrow.
Windows UI is locked up. You might as well hit reset now.
Can't switch to other windows on task bar, but can minimize any open windows.
Once all open windows are minimized, there is nothing left to do other than reset.

Expected Results:  
Viewed mail message.

Comment 1

[Andrew Schultz]

we only need one bug report per bug.  you can add additional comments in the bug
using the "Additional Comments" box.

marking as a dupe

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