Closed Bug 63551 Opened 24 years ago Closed 24 years ago

reply of big message takes a *really* long time.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 22486

People

(Reporter: jelwell, Assigned: bugzilla)

Details

I have an email message with a CC list that can not be rendered fully even in
full screen mode. 5 scrolling pages, 3 to 4 emails across. I can't post the
email addresses here because many are nonpublic.

This email, and any replies (to all) cause the app to freeze up while
displaying. tested on linux comm build 2000122108.
change qa contact to myself
QA Contact: esther → sheelar
does it freeze, or does it take a *really* long time?  try again and give it a
few minutes.

what are the specs on this machine?  (CPU and RAM)

we have some major performance problems with reply.

re-assigning to ducarroz.

perhaps you can you copy the original message to a local folder and email him
the file so he can try to reproduce it.
Assignee: sspitzer → ducarroz
Summary: Large CC list causes freeze up of Mail Window. → Large CC list causes freeze up
it doesn't freeze forever. If I wait long enough, the application will come back 
alive - and just be really slow, until I move to another message. I'll email 
ducarroz@netscape.com the message.
Summary: Large CC list causes freeze up → Large CC list takes a *really* long time.
don't bother.  this is a known bug.  I'll go find out the bug number.
note, it's not the cc list, it's the big body.

I couldn't find the reply bug, but I know it exists.
Summary: Large CC list takes a *really* long time. → reply of big message takes a *really* long time.
The size of the message is actually quite small.
But since the body is small, but the number of cc's is big it might be something
else. 

we may have performance problems with populating the addresses.

leaving for ducarroz to decide.

thanks for the extra info, joe.
#22486 is the reply performance bug.
stephen,
changed qa contact as you because performance is your area.
QA Contact: sheelar → stephend
This is something that shows up in my testings, for example on a P133 with 64
megs, it takes us 25 seconds to reply to to a 2k HTML message with 5 recipients.
 Sounds like Joe's problem.  Marking a DUP.

*** This bug has been marked as a duplicate of 22486 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
VERIFIED DUP.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.