Message view window has header and preceding message's body text appended to it
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: thee.chicago.wolf, Unassigned)
Details
This is a tough one to describe or give STR to repro but, at the very least, ensure you have View > Headers > All selected.
What I am seeing is a kind of bleed-over from a succeeding message in the message list. In one message I got, I see the header and the message body of the message just above it and, I am just now discovering, some bleed-over from the body of a message two higher.
Sorry if this is not making sense. Let me try again. I have three massages that arrived at 2:38PM, 2:39PM and one at 2:41PM. They are the top-most and current messages in my Inbox for this account. When I click on the message that arrived at 2:38PM, in it's message body, I see it's own intended message as I scroll down. But if I scroll down more, I ALSO see the header and message body of the email that arrived at 2:39PM. If I scroll all the way to the end, I ALSO see the header and message body of the email that arrived at 2:41PM.
|
Reporter | |
Comment 1•3 years ago
•
|
||
As an experiment, I sent myself a new message to the account exhibiting the behavior. When I click on the specific email that is showing this behavior, the message I just sent from another account got appended to the body of the culprit email.
I'm willing to send this offending email privately to someone as proof that I am not going nuts.
Full disclosure, I installed 94.0b5 this morning.
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 2•3 years ago
|
||
Shortly after getting a message and it seems to append yet more to the culprit email, error console shows this but not sure if it's related:
15:25:01.037
mail.activity: Exception: [Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/ActivityManager.jsm :: getActivity :: line 135" data: no] ActivityManager.jsm:86:16
removeActivity resource:///modules/ActivityManager.jsm:86
onFolderRemovedFromQ resource:///modules/activity/autosync.jsm:247
_timerCallback resource:///modules/AppIdleManager.jsm:30
15:25:01.039 mail.activity: onFolderRemovedFromQ: [Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/ActivityManager.jsm :: getActivity :: line 135" data: no] autosync.jsm:257:22
15:25:01.039
NS_ERROR_NOT_AVAILABLE: ActivityManager.jsm:135
getActivity resource:///modules/ActivityManager.jsm:135
removeActivity resource:///modules/ActivityManager.jsm:84
onFolderRemovedFromQ resource:///modules/activity/autosync.jsm:247
_timerCallback resource:///modules/AppIdleManager.jsm:30
|
|
Reporter | |
Comment 3•3 years ago
|
||
Confirming that it's happening whether header is set to All or Normal.
|
||
Comment 4•3 years ago
|
||
So you're saying you have a reproducible case? That would be very helpful! Please send me a sample message.
|
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #4)
So you're saying you have a reproducible case? That would be very helpful! Please send me a sample message.
*** This bug has been marked as a duplicate of bug 1734847 ***
Yup. And in trying to get it to you, TB almost locked up my machine! I'll send it to you privately. Be warned, it's big and might lock up TB.
|
|
Reporter | |
Comment 6•3 years ago
|
||
I forgot to mention that as a byproduct of this bug, I also lost permanently one email message. I had accidentally deleted it while INTENDING to do an Edit As New Message action to a it via the [GMail] > Sent Mail folder but when I did a CTRL-Z to return it to the Sent Mail folder from the Trash, it returned as a munged message with some garbage header info inserted into it and the message body essentially wiped out.
|
|
||
Comment 7•3 years ago
|
||
Got the sample. What should I do to reproduce? Put that into a local folder, then click on the message in the list?
|
|
Reporter | |
Comment 8•3 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #7)
Got the sample. What should I do to reproduce? Put that into a local folder, then click on the message in the list?
If you're able to, try putting it into the [GMail] > Sent Mail folder and then send a generic message to the account that holds the message. In my case, the new incoming message gets appended to the example I sent. You'll know it worked if you scroll to the very bottom of the message and see your test message there. Maybe it'll only work since it's tied to my account but give it a try. Hope springs eternal? =)
|
|
||
Comment 9•3 years ago
•
|
||
Could not reproduce with the received message.
Looks like the message (2020 baseball .... ) is just representing the corruption. In the saved .eml the message is pulled together with another(s), it does like
[old message]
--000000000000ef2fe605cf569511--
Delivered-To: fooo@gmail.com
[further headers and content from next mail]
|
|
Reporter | |
Comment 10•3 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #9)
Could not reproduce with the received message.
Looks like the message (2020 baseball .... ) is just representing the corruption. In the saved .eml the message is pulled together with another(s), it does like
[old message]
--000000000000ef2fe605cf569511--
Delivered-To: fooo@gmail.com[further headers and content from next mail]
Yeah, that's what I thought was going to happen if you tried to repro. Whatever damage is being done it probably has to be on my setup. Is there any kind of logging I can do? Maybe I can catch it in the act somehow?
|
|
Reporter | |
Comment 11•3 years ago
•
|
||
(In reply to Magnus Melin [:mkmelin] from comment #9)
Could not reproduce with the received message.
Looks like the message (2020 baseball .... ) is just representing the corruption. In the saved .eml the message is pulled together with another(s), it does like
[old message]
--000000000000ef2fe605cf569511--
Delivered-To: fooo@gmail.com[further headers and content from next mail]
Magnus,
I just bumped up to the test build of 95.0b1 to see if anything's improved. Sadly, the appending issue is still present in 95.0b1. I noticed one thing. One of the emails that I have which is mangled beyond recognition now almost freezes TB and memory use jumps up to almost 8GB. I managed to get a memory snapshot. Is that of any value here?
|
|
Reporter | |
Comment 12•3 years ago
|
||
So I can reliably repro this mega-memory consumption by replying to one of these mangled emails, saving it to Drafts and then attempting to edit the Draft. Nothing in Error Console sadly.
|
|
||
Comment 13•3 years ago
|
||
I think we just have to figure out the regression for the mangling. Probably not anything to log or do memory analysis on. The memory consumption is likely just a cause of reading from the wrong place in the damaged file, or something like that.
Description
•