171251 - Hangs when reading a message sent from AOL client with a background image

Status: VERIFIED DUPLICATE of bug 98626

(MailNews Core :: Backend, defect)

Description

[Cavin Song]

BUILDID: 20020926 trunk build.

It does not matter if the attached message is in a local folder or IMAP folder, 
when read, it uses up 100% CPU (you can see it in Task Manager) and when you 
click on any other message or folder nothing happens and so you have to kill and 
restart the program.

The behavior is different for the 1.0 branch build. When read, it still uses up 
100% CPU but when you click on another message or folder it displays that 
message or open the selected folder.

Another problem I found related to this is that if you delete a message listed 
in front of the troubled message (ie, the deleted message is moved to Trash 
folder and the troubled message is displayed in the message pane and you can't 
do anything anymore) you would lose the deleted message because when you kill 
and restart the program you'll find that the message you deleted is not in the 
Trash folder either.

This problem may be related to bug 171083 but I'm not sure.

Comment 1

[Cavin Song]

Attachment: Msg causing the problem

Put this message in the local folder, read it and you should be able to
reproduce the problem.

Comment 2

[Cavin Song]

Hmm, seems like the problem is fixed by 09/27 build.

Comment 3

[Gayatri Rimola]

Is this problem on the branch as well?

Comment 4

[laurel]

worksforme in sep30 commercial branch, win98.
Haven't we had some other general problems with some background image messages
(i.e. non-aol)?  I seem to recall a few, particularly editing such messages
(drafts,templates) or opening to standalone if already open in 3-pane... but I'm
not sure of the status of the others.
Anyway, this one worksforme on today's branch.

Comment 5

[Cavin Song]

It was a trunk only problem and seems to be fixed by the 09/27 build as well.

Comment 6

[yulian chang]

No problem reading the message (from C#1) using 20020926 trunk build on WinNT.
Probably the problem was related to Bug 98626 which had been fixed in 9-26 trunk
builds.

Comment 7

[laurel]

Also covered in bugscape bug 20194?

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

Comment 8

[laurel]

Sorry, didn't mean to resolve

Comment 9

[scottputterman]

I think this is a dup of 98626

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

Comment 10

[laurel]

marking verified as duplicate