Closed
Bug 243924
Opened 20 years ago
Closed 13 years ago
Long delay before messages are rendered
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: eyalroz1, Unassigned)
References
Details
(Keywords: testcase-wanted)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040513 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040513 For the last two weeks or so I've been experiencing delays from the moment I click a message in the message list to the moment it is rendered in the message display pane. This was not the case previously. My box is reasonably fast (Athlon 1400 MHz = 1600 XP ; 256 MB memory). I do not see a spike in CPU usage, though... weird. This happens for both RTL and LTR messages. I managed to screen capture one particularly nasty delay in which a message began to be rendered and then just stopped for a while (see screenshots). This does not happen for all messages all the time. Sometimes when I return to the same message it renders fast, normally. Other times it does not. Reproducible: Sometimes Steps to Reproduce:
Reporter | ||
Comment 1•20 years ago
|
||
Reporter | ||
Comment 2•20 years ago
|
||
Reporter | ||
Comment 3•20 years ago
|
||
More info: - this happens for both text and HTML messages - delay is about 1 - 1.5 seconds - this bug may be, but probably isn't, related to bug 200054
Comment 4•20 years ago
|
||
Does the problem occur with a freshly created profile? is it reproducible with other Mozilla versions (e.g. 1.6 or 1.7RC2)? Prog.
Reporter | ||
Comment 5•20 years ago
|
||
(In reply to comment #4) > Does the problem occur with a freshly created profile? Yes. > is it reproducible with > other Mozilla versions (e.g. 1.6 or 1.7RC2)? With 1.7RC2 - no.
Comment 6•20 years ago
|
||
Ok, I would like to reproduce this bug. So just to be sure, all I have to do is use the latest trunk build to read my mail? Prog.
Reporter | ||
Comment 7•20 years ago
|
||
Uh... I... guess so... although I would think if this were more wide-spread someone would have reported it by now. So maybe it does relate to my personal configuration somehow.
Comment 9•20 years ago
|
||
WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040513 - I downloaded the last build of the 13th, which should be pretty close to the one you're using. Can you narrow down this slowdown to rendering rather than to communication with the server? Prog.
Comment 10•20 years ago
|
||
It's easily seen (by me, anyway) by simply switching between the various Message Body As modes. Also View|Source. Boris' suggested dupe is doubtless correct.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 11•20 years ago
|
||
(In reply to comment #7) > Uh... I... guess so... although I would think if this were more wide-spread > someone would have reported it by now. So maybe it does relate to my personal > configuration somehow. This logic doesn't hold. I wrote a similar bug a few YEARS ago. I suggested that Mozilla (and now TB) should at least clear the message pane until the message is displayed. I often cannot tell when the body matches the selected message.
Updated•19 years ago
|
Assignee: sspitzer → mail
Comment 12•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 13•19 years ago
|
||
This bug is a daily annoyance. It happens on several computers, across all platforms, and across all servers. I got a message today that said, "This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code." Just because nobody else has said, "me too," doesn't make it a non-issue! Please fix this bug! It has been outstanding for too long!
Reporter | ||
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 14•13 years ago
|
||
did anyone still see this in SM 1.1? (not interested in 2.0 - that has new potential problems that we don't want to conflate) testcase is lacking
Keywords: testcase-wanted
Whiteboard: [closeme 2011-03-21]
Comment 15•13 years ago
|
||
No response to requested information. Closing as incomplete report.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•