Closed Bug 107275 Opened 23 years ago Closed 23 years ago

hang displaying messages with MANY email addresses

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 64764

People

(Reporter: jthg, Assigned: sspitzer)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5) Gecko/20011011 BuildID: 2001101117 Mozilla stops responding for a long time (1 minute) when viewing messages that are addressed to many people. For example, I got a messaged addressed to me and > 1300 other people which caused the hang. Reproducible: Always Steps to Reproduce: 1. receive a message addressed to MANY (>1000) people 2. try to view the message Actual Results: it should display the message within a second Expected Results: it took a minute and all windows of mozilla stopped responding The next message viewed after viewing this one took a long time (15 seconds). I would think this would imply that a lot of dynamic memory was allocated and now is being deallocated... In fact, mozilla on my sytem usually takes about 30 megs of my memory; but, when I view this message, it jumps to around 130 megs. After the message is viewed, it jumps down to 60 megs - memory leak? If the message is not viewed (view frame is collapsed), I can switch to different messages without a hitch.
BTW, you cannot see all the e-mail addresses even if you click on the little down arrow. Should I file another bug on this? I think there is bug on not being able to see the all the addresses already - but, that might have just been an hallucination of mine...
I am sure that this is a duplicate of Bug 64764 Sorry for reporting a duplicate. *** This bug has been marked as a duplicate of 64764 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup. no worries, it was a good report. better to file a good dup than no bugs at all.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.