Closed
Bug 184712
Opened 22 years ago
Closed 22 years ago
UI unresponsiveness when reply (quoted) to email with large text/plain attachment
Categories
(MailNews Core :: Attachments, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 161775
People
(Reporter: jeff.morriss, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 Sometimes I receive emails with large text/plain attachments (such that the attachments are displayed inline below the sender's text). When I reply to the email, the Mozilla UI becomes unresponsive for quite a while (depending on the size of the attachment). It would appear that during this time Mozilla is formatting the (quoted) attachment in the reply email. There is no (audible) disk activity while this is happening. Forwarding the email yields a lot of disk crunching but the UI remains responsive. Personally I think attachments which are displayed inline should not be quoted in reply emails, but at the very least the UI should remain responsive while it is being quoted. Reproducible: Always Steps to Reproduce: 1. Receive an email with a large (5 Mb) text/plain attachment 2 [review]. Verify that the attachment is displayed inline below the sender's text 3. Hit "Reply" Actual Results: For a 5 Mb attachment, my PII-400 MHz (??) Windows 2000 machine spent 5 or more minutes creating the reply window. During this time the UI was completely unresponsive; I couldn't even browse the Bugzilla database while I was waiting ;-). Potentially of interest is that the mozilla.exe program grew from 90 to 110 Mb of memory usage (according to Windows' Task Manager) and then shrank back to 90 Mb. Expected Results: I would expect the UI to remain responsive during this time. Personally I also don't think inline attachments should be quoted in replies at all, but I'd be happy with the UI remaining responsive.
Reporter | ||
Comment 1•22 years ago
|
||
Nuts! This is a duplicate of bug 161775. I swear I searched for possible dups... I have no idea why I didn't find 161775 until now. *** This bug has been marked as a duplicate of 161775 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
QA Contact: yulian → stephend
jeff, this might be the same as bug 184550. can you confirm? is this fixed for you now? thanks.
verified dup, then. (of bug 161775, for now)
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 4•22 years ago
|
||
Sorry... I'm not ignoring you, I'm just waiting for a stable (non-Alpha or Beta) version of 1.3 to come out. I use Mozilla Mail/News only at work (Customer Support) where it is "on the critical path" (e.g., I can't mess around with it: if it's not stable, I'm screwed). Plus, I'm already feeling a little burned (I had to downgrade to 1.01 because 1.2.1 is unusably slow), so I'm being a little more cautious... Once I try 1.3 I'll put a note here to see if it works...
Reporter | ||
Comment 5•21 years ago
|
||
Sorry for the delay (in case anyone is still watching this bug). This problem is still present in the 1.3 release. Test is still the same.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•