(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 4GB. I managed to get a memory snapshot. Is that of any value here?
Bug 1738105 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(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?